New answers tagged scalability
I use a different approach. With PowerDNS the replication of zones and records is quite easy. The whole dns-data is stored in a MySQL-DB and is replicted via MySQL to 2 slave servers, which also use powerdns. This setup ran for about 6 years without any problems. BTW: bind is still used for caching
As sysadmin for an environment with dozens of DNS servers and thousands of domains, I feel (well, felt) your pain. We solved it with puppet and templates. All our domains and servers also have entries in our infrastructure database (even the zones get generated from there, but that's irrelevant for now). So we do roughly the following: Master nameservers: ...
Some suggestions could be: Create a caching only DNS server like the one described in this article ? Copy over periodically the configuration from one slave to the other(s) with rsync Use heartbeat or keepalived to make a load balancing primary DNS server for a same IP.
Top 50 recent answers are included