"In this tutorial I will describe how to install and configure MyDNS, a DNS server that uses a MySQL database as backend instead of configuration files like, for example, Bind or djbdns. This has the advantage that you can easily use web-based frontends to administrate your DNS records. MyDNS simply reads the records from the database, and it does not have to be restarted/reloaded when DNS records change or zones are created/edited/deleted! I will also show how to set up a secondary DNS server, but I will not use normal zone transfers to get the records from the primary to the secondary DNS server; instead, I will use MySQL database replication. I will simply replicate the data from the primary to the secondary server."
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2005-07-14
Yes, that is all true, but realize that if you lost your mySQL server for couple of hours for some reason, it is quite possible that you DNS system (servers) is sgoing down with it. What good is mail server and web server when there are no DNS server resolving MX and A records 
So I think it is easyer to setup secondary BIND server like setup secondary myDNS + mySQL server independent on that first and master mySQL and myDNS server... that has also exact the ZONES like the first server. in this case you need to run TWO mySQL servers and synchronize them
As I said myDNS is GREEAT, but I only talking about my 6 months experience with myDNS in mission critical applications
It`s only my point of view anyway myDNS is GREAT software! it was very usefull for me when I migrated from Windows 2000 to BSD servers...
Member since:
2006-01-22
Yes, but bind is very slow when compared to bind-dlz... and bind-dlz (even non-dynamic bdb) is slow compared to MyDNS. I am able to do 20k queries a second with MyDNS (postgres backend).
On the other hand, I can understand why someone would want to run bind for the sake of reliability.. but there is a sacrifice!