Changes

Tasks:

* Configure named.conf to allow dynamic DNS update to the ddns sub-domain zone file

* Create the initial forward-mapping and reverse-mapping zone files for dynamic DNS update

* If your domain is called "mydomain.com", create a sub-domain called "ddns.mydomain.com".

* Set aside the network 172.16.101.0/24 for the "ddns" sub-domain.

* Add the "forward-mapping" and "reverse-mapping" zones for the new sub-domain to your named.conf file. If the new sub-domain is "ddns.mydomain.com", use the same name for the forward-mapping zone name. If all the hosts in the sub-domain are in the same network "172.16.101.0/24", use "101.16.172.in-addr.arpa" for the reverse-mapping zone name. Use the following file names for the forward-mapping and reverse-mapping zone file:

* Replace "ddns.mydomain.com" and "101.16.172.in-addr.arpa" with your own zone names.

* Create the initial forward-mapping zone file: db-ddns.hosts:

* Start (or re-start) the "named" daemon (service named restart), if it does not complain, go to next step, otherwise check the contents of "named.conf", "db-ddns.hosts" and "db-ddns.rev". You should also check the file "/var/log/messages" for diagnostic messages. There are two utilities that come with the "bind" package, they are "/usr/sbin/named-checkconf" and "/usr/sbin/named-checkzone". You can use "named-checkconf" to check for "typo" or syntax errors in "named.conf" and use "named-checkzone" to check for errors in your zone files. Look up the man page on how to use these two time-saving utilities.

* Try "nslookup" to verify that your DNS server answers queries (the static zone information) properly.

# What rpm package contains the "nsupdate" command?