Installing and Administering Internet Services

100 Chapter 3

Conﬁguring and Administering the BIND Name Service

Troubleshooting the BIND Name Server

This section tells you how to identify and correct problems with the

BIND name server. It contains the following sections:

• “Troubleshooting Tools and Techniques” on page 100

• “Problem Symptoms” on page 102

• “Name Server Problems” on page 104

• “Understanding Name Server Debugging Output” on page 109

• “Name Server Statistics” on page 112

NOTE After you conﬁgure the BIND name service on your network, the

following failures may occur:

(1) rcp and remsh may fail with permission denied messages.

(2) rlogin may prompt you for a password.

These problems are the result of switching to domain names. To correct

these problems, you will need to update other network ﬁles. See

“Updating Network-Related Files” on page 95.

If you want to run both BIND and HP VUE, you must have an

/etc/resolv.conf ﬁle on your system, or HP VUE will not start. See

“Conﬁguring the Resolver to Query a Remote Name Server” on page 91.

After you conﬁgure the BIND name service, sendmail will use the name

server’s MX (mail exchanger) records for mail routing. See “Installing and

Administering sendmail” on page 117 for information on sendmail.

Troubleshooting Tools and Techniques

This section describes the available tools for troubleshooting of the BIND

name server.

The ping command

Use the ping command to test whether a speciﬁc host name can be

looked up. You can also use it to check network connectivity to the name

server.

$ /usr/sbin/ping hostname