Agenda: dns-nsd-config.txt

Configuring NSD

1. Log in using SSH/Putty/... to your AUTH machine:

    $ ssh -l adm auth.grpXX.ws.nsrc.org

2. On AUTH:

    # cd /usr/local/etc/nsd/

        Let's make a directory for slave zones to go into:

        # mkdir slave
        # chown bind slave

        Let's copy the default configuration file:

    # cp nsd.conf.sample nsd.conf
        # chmod 644 nsd.conf

    Now edit the file nsd.conf, and make the following changes:

        - find the line:

                # database: "/var/db/nsd/nsd.db"

        and uncomment it (remove # in front):

                database: "/var/db/nsd/nsd.db"

        - fid the line:
        
                # identity: "unidentified server"
        
        and change it to:

                identity: "nsd 3.2.7"

        - find the line:
        
                # zonesdir: "/usr/local/etc/nsd"

        and change it to:

                zonesdir: "/usr/local/etc/nsd"

        - find the line:

                # verbosity: 0
        
        and change it to:

                verbosity: 1

        - Now let's add a slave for your TLD zone.  Insert the following lines,
        at the end of the file, replacing the appropriate values for your own
        zone:

- - - - - - - - - - - - - - - cut below - - - - - - - - - - - - - 
zone:
        name: "MYTLD"
        zonefile: "slave/MYTLD.zone"

        # Master server - replace X with the group of your master NS
        allow-notify: 10.10.X.1 NOKEY
        request-xfr: AXFR 10.10.X.1 NOKEY

- - - - - - - - - - - - - - - cut above - - - - - - - - - - - - - 


        - Save the file, exit

3. Start NSD!

        - edit /etc/rc.conf and add:

    nsd_enable="YES"

    # /usr/local/etc/rc.d/nsd start 

4. Rebuild and reload NSD's base

        # nsdc rebuild

        You will see something similar in the output:

...
warning: slave zone ocean with no zonefile 'slave/MYTLD.zone'(No such file or directory) will force zone transfer.
...

        # nsdc reload

        # tail /var/log/daemon.log

        You should see something similar:

...
Feb 17 07:26:00 auth nsd[12332]: xfrd: zone MYTLD written received XFR from 10.10.X.1 with serial 2011027618 to disk
Feb 17 07:26:00 auth nsd[12332]: xfrd: zone MYTLD committed "xfrd: zone MYTLD received update to serial 2011027618 at time 1297898760 from 10.10.X.1 in 1 parts"
...

        Make NSD write the file to disk:

        # nsdc patch

        You should see something like:

writing zone MYTLD to file slave/MYTLD.zone

        Verify it is the case:

        # ls -l slave/

-rw-r--r--  1 root  wheel  414 Feb 17 07:28 MYTLD.zone

5. Test that your new secondary is answering:

        # dig @127.0.0.1 MYTLD SOA


6. If all is OK, add "auth.grpX.ws.nsrc.org" to your list of NSes in your
   zone on the MASTER host - remember the serial!


   ... when you modified the zone on MASTER, it should have
   sent a notify to AUTH regarding the zone change, and AUTH should
   have picked up the new version.

   To verify that AUTH has picked up a new copy of the zone:

   # dig @auth.grpX.ws.nsrc.org SOA MYTLD
   # dig @auth.grpX.ws.nsrc.org NS MYTLD

   Make sure you see all NSes, including auth.grpX !

   Q: What else do you need to do to make your new NS public ?