up vote 0 down vote favorite
share [g+] share [fb]

I am looking for an Iterative Resolver server - a server that would handle the DNS resolutions for PC users in an environment. I am well aware of the Microsoft DNS and Bind, and also of free services like Google DNS and OpenDNS.

However, I am looking for alternative solution which I can install on premise. Any suggestions recommendations? (paid - free - or open source)

link|improve this question
62% accept rate
Looking for a bit of insight: What's wrong with MS DNS or BIND? They both fulfill the requirements of your question. – Chris S♦ Aug 31 '11 at 14:54
MS DNS won't do DNSSEC validation, if that matters. – Alnitak Aug 31 '11 at 15:28
Is not about what is wrong with MS or Bind. They all have pros and cons. I did not want to be stuck with selecting between the two, I wanted to test alternatives. – GeorgeU Sep 7 '11 at 21:13
feedback

2 Answers

up vote 1 down vote

I usually install a linux box with unbound to act as a resolver for the network. It's simple enough to configure on Debian: just install the system, then unbound and make it listen on the LAN interface instead of 127.0.0.1.

link|improve this answer
feedback
up vote 0 down vote

Both Bind and Microsoft's implementation can be - and usually are - installed on premise. Bind is also free, and requires a U*X like operating system, usually linux, though I think I remember a windoze implementation existed. MS's' comes with any "server" OS (not free). (If you chose the linux path, you will also find there's a smattering of "lite" resolvers you could use instead of bind.)

So before we probe any further, could you clarify why MS/Bind do not satisfy you?

Cheers

link|improve this answer
BIND does exist for Windows, as does Unbound. – Alnitak Aug 31 '11 at 15:21
I simply wanted to test and compare different solutions. Did not want to be stuck to those default 2 DNS resolver solutions. – GeorgeU Sep 7 '11 at 21:10
If so, then dnsmasq (linux) may be for you. It also bundles a dhcp server (which I believe can be turned off). There is also something called (I think) djbdns, which I cannot stand in the least - but then, I cannot stand qmail, either (same author/philosophy). If you like qmail, you may want to look into that. As far as "stuck" goes, BIND was - and still is, AFAIK - the reference implementation for nameservers. Please also note that, in AD - or even windows domain - situations, turning off nameserving in the DC is a real PITA. – Alien Life Form Sep 14 '11 at 7:09
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.