Configuring the Domain Name Service (DNS)

Troubleshooting DNS

After configuration, DNS starts automatically if /etc/named.conf is present. When named starts up, it writes its process id to the file /etc/ This is useful to programs that want to send signals to named.

If you encounter problems with named, first view the logfile /usr/adm/syslog for any errors. If none are found, use the Name Daemon Control program, ndc(ADMN), to troubleshoot DNS without restarting the named process. Options for /etc/ndc include:

ndc reload
Causes named to read named.conf and reload the database, overwriting cached data. This is useful when you make a change to a data file and you want named's internal database to reflect the change.

The reload option also has the effect of scheduling all secondary zones for serial-number checks, which could lead to zone transfers ahead of the usual schedule. Normally, serial-number comparisons are done only at the intervals specified in the zone's SOA record.

ndc dumpdb
Dumps the current database and cache to /var/tmp/named_dump.db. This gives you an indication to whether the database was loaded correctly.

ndc trace
Turns on debugging. Each following USR1 increments the debug level. The output goes to /var/tmp/

ndc notrace
Turns off debugging completely.

ndc querylog
Toggles tracing of all incoming queries. The trace is sent to /usr/adm/syslog and provides a large amount of data. The ndc qrylog option also works.

Next topic: Using nslookup
Previous topic: Administering and troubleshooting DNS

© 2007 The SCO Group, Inc. All rights reserved.
SCO OpenServer Release 6.0.0 -- 05 June 2007