Question

I'm working on migrating to Amazon EC2 for our servers and need to try out internal DNS options. I'm looking for the equivalent of Tomcat (a standard well know easy to use servlet container) in the DNS area. BIND is the only one I'm familiar with by name, but I'm wondering if there are other "better" options or if that's the one I should go with.

Our servers are currently running CentOS.

This will end up being a production environment so stable software is a requirement.

Was it helpful?

Solution

BIND is the usual nameserver software that is used, but there is also djbdns and a few others.

I must also recommend the book DNS and BIND if you go the BIND route, it helped me a lot back in the day. I hope it's been updated since though, considering the more recent updates to BIND.

OTHER TIPS

I'd recommend Bind, even though the syntax is a bit scary at first. I used this guide, when I was first learning Bind: http://tldp.org/HOWTO/DNS-HOWTO.html

There are other options, like PowerDNS and if you're working with a big environment you might want to consider LDAP for backend.

On CentOS, it's probably easiest to just use yum to install bind and then go through the guide above.

I recommend BIND, because it's the best documented and most well understood, and NSD, because it's good and free.

In particular, NSD is only an authoritative name server, so doesn't have to carry the cruft that other servers that attempt to provide all of the different DNS functions have.

I seriously couldn't ever recommend djbdns - notwithstanding that it's now in the public domain, the author simply refuses to implement many parts of the standard DNS protocol (such as AXFR).

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top