There’s a DO tutorial about setting up ‘dns slave auto configuration’ however it doesn’t explain why i would want to do it, and what it actually accomplishes. Can you explain. For example,
is the master/slave set up described in the article going to make a duplicate copy of all the data, or does it have nothing to do with copying the database?
will it result in higher performance somehow?
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Click below to sign up and get $100 of credit to try our products over 60 days!
<pre>What benefit does that provide?</pre> <br> <br>Here’s a decent article on the topic: <a href=“http://www.dummies.com/how-to/content/considering-dns-server-design.html”>Considering DNS Server Design</a>
<pre>…but then why would I want to do it? Why do I want to copy DNS records from the master server onto the slave server?</pre> <br> <br>Because even the mighty GoDaddy* (*substitute whatever DNS provider you’re using, here) has outages from time-to-time.
You should have at least one slave DNS server for redundancy so it can be used instead of the other one if it’s down. <br> <br>Setting it up as a slave server takes care of copying the DNS records so you don’t have to set up a completely separate ns2 DNS server and add each DNS record twice, once on each server.
Thanks Pablo but then why would I want to do it? Why do I want to copy DNS records from the master server onto the slave server? What benefit does that provide?
@m73mitchell, <br> <br>Take a 2nd look at the title of the article you cited: “How to Setup <strong>DNS Slave</strong>…” The configuration outlined in that article only copies DNS records from the master server onto the slave server(s). <br> <br>Thus, it will not “keep a copy of the master if (sic) the database on each server.”
But how does the slave keep a copy of the master if the database on each server isn’t linked?