HP-UX IP Address and Client Management Administrator's Guide HP-UX 11i v2, HP-UX 11i v3

Do not insert a trailing dot at the end of the domain name.
2. Set the HOSTNAME variable in the /etc/rc.config.d/netconf file to the same value, as
specified in the following example:
HOSTNAME=indigo.div.inc.com
Master Server Configuration File
The configuration file, /etc/named.conf, informs the master server of the location of all the
required data files. The master name server loads its database from these data files. The
hosts_to_named program creates the named.conf file.
Following is an example configuration file for a master server authoritative for the domain
div.inc.com, and for the network 15.19.8.
# # type domain source file
# option { directory “/etc/named.data”;
}; zone “0.0.127.IN-ADDR.ARPA” { type master;
file “db.127.0.0”;
}; zone “div.inc.com” { type master;
file “db.div”;
}; zone “8.19.15.IN-ADDR.ARPA” { type master;
file “db.15.19.8”;
}; zone “.” { type hint;
file “db.cache”;
};
Figure 2-1 shows the structure of a master server and a slave server. In the Figure 2-1, the master
server is rabbit.div.inc.com and the slave servers are cheetah.div.inc.com and
indigo.div.inc.com.
Figure 2-1 Structure of a Master Server and Slave Servers
For the setup in Figure 2-1, the /etc/hosts file is as follows:
15.19.8.119 rabbit 127.0.0.1 localhost loopback
15.19.8.64 cheetah 15.19.8.197 indigo incindigo
Use the following parameters for the hosts_to_named command to generate the example
named.conf file for the master server rabbit from the /etc/hosts file:
-d div.inc.com name domain
-n 15.19.8 net address domain
-s rabbit master server
-s cheetah slave servers
-s indigo -Z 15.19.8.119 master server address
-d div.inc.com
The configuration file named.conf is as follows:
// generated by named-bootconf.pl
options { check-names response fail; // do not change this
check-names slave warn; directory “/etc/named.data”; // running directory for named
/* If there is a firewall between you and the nameservers you
* want to talk to, you might need to uncomment the
* query-source directive below. Previous versions of BIND
* always asked questions using port 53, but BIND 8.1 uses
68 Configuring and Administering the BIND Name Service