HP-UX IP Address and Client Management Administrator's Guide (October 2009)

119.8.19.15.in-addr.arpa. (The current origin is appended to the name 119 in
the first field, because it does not end with a dot.)
$TTL Indicates (in seconds) the time to live value for records that do not have the ttl value
defined in the data field.
Adding a Host to the Domain Data Files
You can add a host to the /etc/hosts file and run the hosts_to_named command to
automatically regenerate all the data files for the domain. You can also manually add the host
to all the domain data files.
Use the following procedure to manually add a host to the domain data files:
1. Edit the db.domain file and add an address (A) resource record for each address of the new
host, and add CNAME, HINFO, WKS, and MX resource records as necessary. Then, increment
the serial number in the SOA resource record by 1.
2. Edit the db.net file and add a PTR resource record for each host address. Then, increment
the serial number in the SOA resource record by 1.
3. Add the host to the /etc/hosts file.
CAUTION: If the host is not listed in the /etc/hosts file, and you accidently run the
hosts_to_named command, the db.domain and db.net files are overwritten, and the
host is lost.
See the sections “Master Server db.domain Files” (page 73) and “Master Server db.net Files”
(page 75) for examples of the db.domain and db.net files.
4. After modifying the domain data files, issue the following command to restart the name
server, which forces the name server to reload its databases:
/usr/sbin/sig_named restart
Deleting a Host from the Domain Data Files
You can delete the host from the /etc/hosts file and run the hosts_to_named command to
regenerate all the data files for the domain. You can also delete the host manually from all the
data files.
Use the following procedure to manually delete a host from the domain data files:
1. Edit the db.domain file and delete the A, CNAME, HINFO, WKS, and MX resource records
associated with the host. Then, decrement the serial number in the SOA resource record by
1.
2. Edit the db.net file and delete all the PTR resource records for the host. Then, decrement
the serial number in the SOA resource record by 1.
3. After modifying the domain data files, issue the following command to restart the name
server and force it to reload its databases:
/usr/sbin/sig_named restart
Configuring a Slave Name Server
After configuring the master name server, you must set up the slave server to share the load
with the master server, or to handle the entire load if the master server is down. The
/etc/named.boot file informs the server whether it is a master or a slave server. The difference
between a master server and a slave server is the source from which they obtain the data. The
master server reads its data from files. A slave server loads its data over the network from another
name server, usually the master name server, using a zone transfer. The slave server cannot load
data from another slave name server.
76 Configuring and Administering the BIND Name Service