Hi! If you’ve been reading about DNS on my blog, you probably understand the importance of having DNS services, you have some idea about why you might want to run your own DNS server, and you realize that protecting your online brand means protecting your domain registration. What I’d like to talk about this time is how many DNS servers you should plan to operate.
BIND, which stands for Berkley Internet Name Daemon, is a DNS server that’s been designed to be able to provide every kind of DNS service you might need. It is the most commonly and widely used DNS server in the market, and it’s also open source and free. Technically speaking, you could theoretically run a single BIND server that hosts your internal domain, and provides your users and customers with a DNS resolver. A lot of organizations with limited resources start out this way. But even if you’re forced to start out with a setup like this, it’s not a good idea to keep it like this.
The problem with a one-server-fits-all approach is that if anything happens to degrade your DNS server’s performance, you can impact all of your DNS services. The DNS protocol is designed to run a distributed service with multiple servers sharing the load and making the DNS services very resilient. By splitting the service up among several servers, you insure that a problem with one server does not impact your entire DNS infrastructure.