Previous Page | Next Page

  1. Agustin's Linux Manual
  2. Networks & Servers
  3. About the Author
  4. Table of Contents
  5. IP Addresses Networks and Subnets
  6. Network Classes
  7. IP Address in Decimal Notation
  8. Sub-netting
  9. Designing Subnets
  10. Allocating Subnets
  11. Defining Host Addresses
  12. Variable Length Subnet Mask
  13. Routing Protocols
  14. Classless Internet Domain Routing
  15. Servers - Chapter 9
  16. Apache Web Server
  17. Configuring Apache
  18. Uploading Web Pages
  19. Apache Overview
  20. MIMEMagic
  21. DNS Servers
  22. Welcome to Webmin
  23. Creating the Master Domain
  24. Adding the Reverse Zone
  25. Querying the DNS server
  26. Adding Virtual Domain to DNS Server
  27. Reverse Zone for Virtual Zone
  28. Binding IP Address for Virtual Domain
  29. Virtual Web Hosting
  30. DNS Security Options
  31. FTP Server
  32. Securing the FTP Server
  33. Email Server
  34. Postfix Configuration
  35. Dealing with Identical Users
  36. Configuring Email Clients
  37. Configuring Outlook
  38. Samba Server
  39. Configuring SAMBA Server
  40. The smb.conf File
  41. smb.conf Analysis
  42. Adding Users to Samba

The next step is the Reverse Zone for

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: [/] Add NS record for Master Server?
  6. Email address: root@localhost or
  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: (type complete IP address here)
  4. Host name:
  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:
  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)

  1. Name: www
  2. Time-To-Leave: Default
  3. Real Name:
  4. Click on create
  5. Name: mail
  6. Time-to-Leave: Default
  7. Real Name:
  8. Click on create
  9. Name: ftp
  10. Time-to-Leave: Default
  11. Real Name:
  12. Click on create
    Fig 9.25 After you have entered all the aliases it should look like this
  13. Return to zone list

* Click on Apply Changes

We just completed a totally functional DNS

You can now verify the changes in the main configuration file /etc/named.conf
Note that a new zone has been added.

You should see something similar to this: (Your host of course)

Zone “” { type master; file “/var/named/”; }; zone “” { type master; file “/var/named/168.34.26.rev”; };

Contents of these files in /var/named
This is the content of the file:

$ttl 38400	IN	SOA	root.localhost. (
				1063884851  ;Serial
				10800            ;Refresh
				3600              ;Retry
				604800          ;Expire
				38400 )          ;Minimum	IN	NS	IN	A	IN	MX  10	IN	CNAME	IN 	CNAME	IN	CNAME

This is the content of the file: 168.34.26.rev

$ttl	38400	IN	SOA  root.localhost. (
				1054527626  ;Serial
				10800	          ;Refres	
				3600	          ;Retry
				604800          ;Expire
				38400 )          ;Minimum		IN	NS		IN	PTR	IN	CNAME	IN	CNAME		IN	CNAME

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.