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

nslookup must display a list of all the root name servers in the db.cache file. If nslookup
does not display the root name servers, see “Troubleshooting the BIND Name Server”
(page 92).
6. If you are running syslogd, you can check the error messages in the
/var/adm/syslog/syslog.log file. For more information, see “Troubleshooting the
BIND Name Server” (page 92).
7. Type exit to exit from nslookup.
Updating Network-Related Files
After you configure your system to use BIND, you must update the following network-related
configuration files:
• /etc/hosts.equiv
• $HOME/.rhosts
• /var/adm/inetd.sec
• $HOME/.netrc
The entries that use simple host names in these network-related files are assumed to be in the
local domain. Therefore, you must clearly state the fully qualified domain name for all the hosts
in these files, when the hosts are outside your local domain.
Updating /etc/hosts.equiv and $HOME/.rhosts
You must convert flat or string-type host names that are not hosts in the local domain to fully
qualified domain names in the /etc/hosts.equiv file and in all the $HOME/.rhosts files.
The shell script convert_rhosts, in the /usr/examples/bind directory, accepts input
conforming to the syntax in the /etc/hosts.equiv file and converts it to fully qualified domain
names. The comments specified in the beginning of the script file provide instructions on how
to use this utility.
Updating /var/adm/inetd.sec and $HOME/.netrc
You must convert flat or string-type host names that are not hosts in the local domain to fully
qualified domain names in the /var/adm/inetd.sec file and in all the $HOME/.netrc files.
An automated utility for performing this task is not available, therefore, you must do it manually.
Updating /etc/hosts
To provide an alternate means of lookup when the name server is down, you must maintain a
minimal /etc/hosts file. It must contain the host names and the Internet addresses of the hosts
in your local domain.
Delegating a Subdomain
When your domain reaches a certain size, or you decide to distribute the management of parts
of your domain to various entities within your organization, you can divide the domain into
subdomains. Within your own domain, you can delegate any number and level of subdomains
to distribute control and management responsibility. You need not register these subdomains
with the parent network. The organization that owns a zone or subdomain is responsible for
maintaining the data and ensuring that up-to-date data is available from multiple, redundant
servers.
You can create a subdomain without delegating it by specifying resource records that refer to
the subdomain within the parent’s zone.
86 Configuring and Administering the BIND Name Service