The above information is largely against lots of security and maintainability principles.
Slave/Secondary DNS Server is a server which is like a Load balancer or Backup server of Master/Primary DNS Server, Its takes all DNS query Records/Zones from Master Server.
After we have installed BIND as a master DNS server (NS1) (as explained in my recent post), we can now try to set up a secondary DNS server (NS2) with BIND on Cent OS.
[[email protected] ~]# nslookup Server: 192.168.0.2 Address: 192.168.0.2#53 Name: Address: 192.168.0.1 Now if there's any problem with NS1 you can rest calm because NS2 acts as a backup.
I created another slave DNS & here's the error I've got, I followed the intructions from 1 to 4.
As Slave/Secondary DNS Server is a exact copy of the master DNS server, In case the Master/Primary Server becomes unavailable or server got down due to some reason, till the server gets up the Secondary DNS Server will accept the query without effecting the end user work.
Before configure the Slave/Secondary DNS Server we need to do some changes in our all Master/Primary DNS Server configuration files i.e.
If they don’t have info about such requested query they will pass the request to the Top Level domain (TLD), if TLD say I don’t know the request, may be the authoritative server know your request, it will forward to authoritative servers, here only defined as address .56.