Installing and Administering Internet Services

136 Chapter3

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 136

• “Problem Symptoms” on page 138

• “Name Server Problems” on page 140

• “Understanding Name Server Debugging Output” on page 145

• “Name Server Statistics” on page 148

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 130.

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

123.

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 153 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