HP-UX IP Address and Client Management Administrator's Guide (October 2009)

Statistics are appended to the file. The statistics look similar to this:
time since boot (secs)1273431
time since reset (secs)29802
input packets326031
output packets327165
queries284353
iqueries0
duplicate queries214
responses50109
duplicate responses70
OK answers220220
FAIL answers63919
FORMERR answers0
system queries23
prime cache calls4
check_ns calls4
bad responses dropped0
martian responses0
Unknown query types0
A queries47921
CNAME queries2054
SOA queries8216
PTR queries35909
MX queries10569
AXFR queries424
ANY queries179263
The first two lines print out the number of seconds that the name server has been running and
the number of seconds since the last restart caused by a SIGHUP signal. To convert these values
to days, divide by 86,400 (the number of seconds in a day).
input packets is the number of datagrams received by the name server. The datagrams come
from the resolver code compiled into the services and from queries and responses from other
name servers.
output packets is the number of datagrams sent by the name server. These datagrams are
responses to resolver queries, queries from other name servers, and system queries. Because
queries to other name servers may not be answered, there will probably be more output packets
than input packets.
queries is the number of queries received by this name server. Because the name server can
handle datagram and stream connections, there can be more queries than input packets. The
total number of queries is the sum of all the counts of different query types listed in this statistics
dump, starting with unknown query types.
iqueries is the number of inverse queries. Inverse queries can be used to map a host address
to a domain name, although PTR queries are the normal method. Some versions of nslookup
send inverse queries when they are starting up.
Troubleshooting the BIND Name Server 101