HP-UX IP Address and Client Management Administrator's Guide HP-UX 11i v2, HP-UX 11i v3

The nsquery command displays the Name Service Switch configuration that is currently in use.
Then it displays the results of the query. For more information, type man 1 nsquery at the
HP-UX prompt.
The syslogd Utility
The syslogd utility logs all the informational and error messages to the file
/var/adm/syslog/syslog.log. You can configure syslogd to log the messages to a different
destination. See the HP-UX Internet Services Administrator’s Guide at the URL
http://www.docs.hp.com /hpux/netcom/index.html#Internet%20Services for
more information on syslogd.
Name Server Debugging
By default, all the error messages are logged in the /var/adm/syslog/syslog.log file. You
can configure named to log only the name server messages by specifying the debug level when
you start named.
To turn on named debugging, issue the following command:
# named -d debug_level
The debugging output is written to the named.run file in the name server’s working directory.
You must use controls to start the name server debugging when named is already running, or
if you want to turn off debugging.
To change the debugging level of the name server that is already running at debug level 1, run
the following command:
# rndc trace 2
To turn off debugging on a name server that is already running at debug level 2, run the following
command:
# rndc notrace
You can also kill the named process and restart named with or without the debugging option.
See “Understanding Name Server Debugging Output” (page 95) for more information on the
debugging output. For more information on rndc, see “The rndc Utility” (page 21).
Depending on the amount of information the name server provides, BIND offers various
debugging levels. The lower the debugging level, the less information is written to the named.run
file. Higher debugging levels provide more information, but occupy more disk space. The default
debugging level is 0. The debugging information is cumulative, that is, level 2 includes all of
level 1’s debugging information, and so on.
BIND provides the following debugging levels:
1 This is the most useful debug level. It logs the basic name server operations: zone loading,
maintenance (including SOA queries, zone transfers and zone expiration, and cache cleaning),
NOTIFY messages, queries received, and high-level tasks dispatched.
2 This level logs multicast requests.
3 This level logs the low-level task creation and operation and journal activity, such as when
the name server writes a record of a zone change to the zone’s journal or when the name
server applies a journal to a zone at startup. This level also logs the operation of the DNSSEC
validator and checking of TSIG signatures.
4 This level logs when a master name server uses AXFR because the transferred zone’s journal
is not available.
5 This level logs the view used while servicing a particular request.
6 This level logs outbound zone transfer messages, including checks of the query that initiated
the transfer.
90 Configuring and Administering the BIND Name Service