Data Networking/Fall 2014/Priya/DNS-CONFIG

The following are the steps to be followed in order to configure BIND9 which is the DNS Software and check for the availability of Primary Name Server, Webserver, Secondary Nameserver.

Configuration

                                                                 IP address
 Primary Nameserver              ns1.neunetworks.com            192.168.3.51
 Secondary Nameserver            ns2.neunetworks.com            192.168.3.54
 Webserver                       neunetworks.com                192.168.3.50

1. To check the hosts by using

cat /etc/hosts 

and it is edited as below .

2 To check for IP address of DNS server use

ifconfig 

and set manually to 192.168.3.51 as shown manually

ifconfig command is used to check for the IP address and clearly, It is observed that in this case the IP address is set to static 192.168.3.51

3.Installation of Bind :

sudo apt-get install bind9 used to install bind9

4.To Define forward lookupzone and Reverse lookupzone.

  sudo nano /etc/bind/named.conf.local 

is command used to edit named.conf. local file and apply the changes as below where forward and Reverse files are defined.

5.Create Forward Zone File

Sudo nano  /etc/bind/zones/db.neunetworks.com. 

command is used to edit neunetworks.com file with using the commands below the forward zone file is created.

6.Create Reverse Zone File

 Sudo nano  /etc/bind/zones/db.rev.3.168.192.in-addr.arpa 

command used to edit db.192.168.3 file and following below commands then Reverse Zone file is created.

Starting Bind

Sudo  /etc/init.d/bind9  start 

command is used to start the domain name service

Verify Bind

Verify for Primary server:

nslookup ns1.neunetworks.com

Verify for Secondary Server:

nslookup ns2.neunetworks.com

Verify for Webserver:

nslookup neunetworks.com

To Reverse check the webserver:

nslookup 192.168.3.50

To Reverse check the Primary server:

nslookup 192.168.3.51

To Reverse check the secondary Server

nslookup 192.168.3.54

The Master Server has been configured with Resource records as shown

The Slave server has been configured with Resource records as shown

The DHCP server is used as as (Secondary Server) slave server