A DNS server manages name resolution of computers on a subdomain. For example, going to docs.cslabs.clarkson.edu you are using clarkson.edu's DNS server to find the ip address of cslabs. This would be the CSLabs' DNS server. Now we use the CSLabs' DNS server to find the ip address of docs.
Where are the files?
The files you need to edit are in /var/named/ on Dns1. They link to corresponding files in /var/named/chroot/var/named/. You need to be root to edit these files.
What do the files mean?
The purpose of this file is to look up ip addresses from a name.
game IN A 126.96.36.199 tremulous IN CNAME game
This snippet of the file shows that game.cslabs should be resolved 188.8.131.52. It then goes on to specify that tremulous.cslabs should resolve to the same address as game.cslabs.
The purpose of this file is to look up the name from a ip address.
36 IN PTR game.cslabs.clarkson.edu.
This snippet shows that 184.108.40.206 is game.cslabs.clarkson.edu.
Changing the serial number lets Dns2 know that it should pull the new version of the file. You will find a line:
2011092703 ; serial
in all of the files. This one was last edited the 27th of September 2011 and is the third revision for that day.
How to push the changes to Dns2
Make sure that the serial# has been changed in any edited files. Then run rndc reload on Dns1. This process happens every 15 minutes regardless.
To check that your changes worked properly use the nslookup command. Lets say that you wanted to check game.cslabs. You would run:
root@dns1 ~]# nslookup game.cslabs 220.127.116.11 Server: 18.104.22.168 Address: 22.214.171.124#53 Name: game.cslabs.clarkson.edu Address: 126.96.36.199 root@dns1 ~]# nslookup game.cslabs 188.8.131.52 Server: 184.108.40.206 Address: 220.127.116.11#53 Name: game.cslabs.clarkson.edu Address: 18.104.22.168
This shows that both Dns1 and Dns2 resolve game.cslabs to 22.214.171.124 which is correct.