The name server daemon, /usr/sbin/named, must be running on every primary, secondary,
and caching-only name server.
If
you have configured your system to query a remote name server (that
is, if you have created an /etc/resolv.conf file that directs BIND queries to a name server
on another host), you do not have to run the named daemon on your host.
Before you start the name server daemon, make sure syslogd is running. syslogd logs informational and error messages. For information
on configuring syslogd, see Chapter 2 “Installing and Configuring Internet
Services” in this manual.
Follow these steps to start the name server daemon:
In the /etc/rc.config.d/namesvrs file, set the NAMED environment variable to 1, as follows:
Issue the following command to determine whether named is already running:
If named is not running, issue the following command to
start it:
For more information, type man 1M named at the HP-UX prompt.
Verifying the Name Server |
 |
If you are running syslogd, check the /var/adm/syslog/syslog.log file for error messages. If error messages are
recorded, see “Troubleshooting the
BIND Name Server”.
Start nslookup(1) with the following command:
At the > prompt, issue the server command to force nslookup to use the server you want to test:
> server BIND_server_hostname |
At the > prompt, type the name of a host for the name server
to look up, as in the following example
You should see output similar to the following:
Name Server: indigo.div.inc.com
Addresses: 15.19.14.100, 15.19.15.100
Name: charlie.div.inc.com
Address: 15.19.9.100 |
Look up several host names and IP addresses of hosts
in the name server's domain.
At the > prompt, type the following commands to verify
that your name server can query root name servers:
nslookup should display a list of the root name servers
in your db.cache file. If it does not, see “Troubleshooting the
BIND Name Server”.
Type exit to exit from nslookup.
