The next step is the Reverse Zone for netcontrol.org

Adding the Reverse Zone

1. Click on Create New Master Zone
2. Now the Zone type will be: Reverse
3. Domain name/network: 168.34.26. (The last number is left out which is 58)
4. Records file: Automatic
5. Master server: server2.netcontrol.org [/] Add NS record for Master Server?
6. Email address: root@localhost or root@netcontrol.org
7. Use template: no
8. Refresh time: leave as default
9. Expiry time: leave as default
10. IP address for template: leave blank
11. Transfer retry time: leave as default
12. Default time to leave: leave as default
13. Click on create

Now Edit the Master Zone properties for the Reverse that we just created.

Create Pointer

1. Click on PT
2. Now add Reverse Address Record
3. Address: 168.34.26.58 (type complete IP address here)
4. Host name: netcontrol.org.
5. Update forward: yes
6. Click on Create
   
   Fig 9.23 After creating it should look like this
7. Return to Record Types

Add name Server (NS)

	(This data may be already updated)

1. Zone Name: 26.34.168
2. Name Server: server2.netcontrol.org.
3. Time to leave: Default
4. Click create
   
   Fig 9.24 If already updated should look like this
5. Return to Record Types

Add Name Alias Record (CN)

Zone “netcontrol.org” {
	type master;
	file “/var/named/netcontrol.org.hosts”;
	};

zone “26.34.168.in-addr.arpa” {
	type master;
	file “/var/named/168.34.26.rev”;
	};

Contents of these files in /var/named
This is the content of the file: netcontrol.org.hosts

--------------------------------------------------------------------------------------
$ttl 38400
netcontrol.org.	IN	SOA	server2.netcontrol.org.	root.localhost. (
				1063884851  ;Serial
				10800            ;Refresh
				3600              ;Retry
				604800          ;Expire
				38400 )          ;Minimum
  
netcontrol.org.	IN	NS		server2.netcontrol.org.com.
netcontrol.org.	IN	A		168.34.26.58
netcontrol.org.	IN	MX  10	netcontrol.org.
www.netcontrol.org.	IN	CNAME	netcontrol.org.
mail.netcontrol.org.	IN 	CNAME	netcontrol.org.
ftp.netcontrol.org.	IN	CNAME	netcontrol.org.
--------------------------------------------------------------------------------------

This is the content of the file: 168.34.26.rev

--------------------------------------------------------------------------------------
$ttl	38400
26.34.168.in-addr.arpa.	IN	SOA	server2.netcontrol.org.  root.localhost. (
				1054527626  ;Serial
				10800	          ;Refres	
				3600	          ;Retry
				604800          ;Expire
				38400 )          ;Minimum

26.34.168.in-addr.arpa.		IN	NS		server2.netcontrol.org.
58.26.34.168.in-addr.arpa.		IN	PTR		netcontrol.org.
www.26.34.168.in-addr.arpa.	IN	CNAME	netcontrol.org.
mail.26.34.168.in-addr.arpa.	IN	CNAME	netcontrol.org.
ftp.26.34.168.in-addr.arpa.		IN	CNAME	netcontrol.org.
--------------------------------------------------------------------------------------

As you can see, using webmin is the fastest way to set up a DNS server; or you can sit there all day and type line by line.

Restart the service to activate all changes, or reboot the system.

[root@server2 root]# service named restart

Since we created a perfect master DNS; we now can use our system for almost anything. The same way we created this master DNS you can also create a slave DNS server at a different IP address. By creating a slave DNS, they can replicate the data of each other so that if one of the servers are down, the other one will respond to the queries.

What I am trying to say is that each server including clients in your network can use different IP addresses and will be resolved by your DNS server.