Dns slave server not updating
You may want to consider using two different POP's as well.
For example, we've used San Francisco 1 and New York 1.
With that said, running your own nameservers is a great way to have more direct control over your hosting infrastructure, and assert full control over your DNS records.
As with any new server, it's always important to ensure your system is up to date.
You can verify this by checking for updates using yum as follows: Above, listen-on must be commented to listen on all available interfaces.
Recursion should be turned off to prevent your server from being abused in "reflection" DDo S attacks.
This means that if the server does not know the answer, it will just tell the client (usually some kind of resolving DNS server) that it does not know the answer and give a reference to a server that may know more.
The only aspect worth noting is that active paths for BIND will change to their chrooted equivalents, for example /var/named becomes /var/named/chroot/var/named With Cent OS 6, you will not need to move any files as the package automatically creates hard symlinks to the non-chrooted directories.
In this guide, we will discuss how to install and configure the Bind9 DNS server as authoritative-only DNS servers on Ubuntu 14.04 machines.
We will set these up two Bind servers for our domain in a master-slave configuration.
For the purpose of this guide, it will be assumed you are configuring both a primary and secondary name server.
It is worth noting that if you are managing a large number of domains this may not be the most viable solution, as you will need to manually add domains on both the master and slave nameservers.