Installing and Administering Internet Services

112 Chapter 3
Configuring and Administering the BIND Name Service
Troubleshooting the BIND Name Server
This message was logged from the routine that handles requests. Shown
are the name looked up, the packet ID (used to determine duplicate
requests), and the type (as defined in
/usr/include/arpa/nameser.h). Type 1 is an address query.
resend(addr=1 n=0) -> 128.59.32.1 6 (53) nsid=18 id=1
0ms
Since no response came from 128.59.16.1, the query with nsid 18 was
resent to other servers.
datagram from 15.19.10.14 port 4253, fd 6, len 41 req:
nlookup(cucard.med.columbia.edu) id 1 type=1
Note that this came from the same IP address and port and has the same
length and ID as the preceding datagram. It is a duplicate and thus forw
discards it. These two lines are repeated three times throughout this
trace. The queries came from the same IP address and port, and have the
same ID and length in each case. Thus, these are all the same query. The
resolver sent the query three times because the name server didn’t
respond. The name server detects that the second and third are
duplicates and discards them. (We can tell because the duplicates did not
get to the forw line.)
Name Server Statistics
The name server keeps track of various statistics. You can print these
statistics to the file /var/tmp/named.stats by issuing the following
command:
/usr/sbin/sig_named stats
Statistics are appended to the file. The statistics look similar to this:
1273431 time since boot (secs)
29802 time since reset (secs)
326031 input packets
327165 output packets
284353 queries
0 iqueries
214 duplicate queries
50109 responses
70 duplicate responses
220220 OK answers
63919 FAIL answers
0 FORMERR answers
23 system queries
4 prime cache calls
4 check_ns calls
0 bad responses dropped
0 martian responses