Installing and Administering Internet Services

102 Chapter 3
Configuring and Administering the BIND Name Service
Troubleshooting the BIND Name Server
servers were found for a remote domain, and how many
addresses were found for each server. When a
secondary server checks with the primary to see if the
secondary’s data is up to date, an SOA query is made.
The SOA responses are displayed at this level.
4 This level displays the initial query packet and the
response packets from other remote servers.
5 This level gives more internal operation information,
most of it not helpful.
10 This level shows the packet sent to other servers
during name lookup. It also shows the packet the local
server sent back to the querying process.
At certain debugging levels, the actual packets are displayed. See RFC
1035 for the format of DNS packets. This RFC is in /usr/share/doc.
To turn off named debugging, issue the following command:
/usr/sbin/sig_named debug 0
See “Understanding Name Server Debugging Output” on page 109. For
more information, type man 1M sig_named or man 1M named at the
HP-UX prompt.
Dumping the Name Server Database
The name server dumps its current database and cache to the file
/var/tmp/named_dump.db when you issue the following command:
/usr/sbin/sig_named dump
For more information, type man 1M sig_named or man 1M named at the
HP-UX prompt.
Problem Symptoms
This section describes symptoms of common name server problems, and
lists possible problems to check for. A description of the problems
appears in the next section, “Name Server Problems” on page 104.
• After configuring the primary server for the first time, names in the
local domain cannot be found. Check the following:
• Problem 2, Syntax Errors
• Problem 1, Incorrect hosts_to_named Parameters