Table of Contents
ndc - name daemon control interface
ndc directive [...]
This command allows the name server administrator to send various signals
to the name server, or to restart it. Zero or more directives may be
given, from the following list:
- status
- Displays the current status of named(8)
as shown by ps(1)
.
- dumpdb
- Causes named to dump its database and cache to
/var/tmp/named_dump.db (uses the INT signal.)
- reload
- Causes named to check the serial numbers of all primary and
secondary zones and to reload those that have changed (uses the
HUP signal.)
- stats
- Causes named to dump its statistics to /var/tmp/named.stats
(uses the IOT or ABRT signal.)
- trace
- Causes named to increment its ``tracing level'' by one. Whenever
the tracing level is nonzero, trace information will be
written to /var/tmp/named.run. Higher tracing levels result in
more detailed information. (Uses the USR1 signal.)
- notrace
- Causes named to set its ``tracing level'' to zero, closing
/var/tmp/named.run, if it is open (uses the USR2 signal.)
querylog Causes named to toggle the ``query logging'' feature, which
while on will result in a syslog(2)
of each incoming query (uses
the WINCH signal.) Note that query logging consumes quite a
lot of log file space. This directive may also be given as
qrylog.
- start
- Causes named to be started, as long as it isn't already running.
- stop
- Causes named to be stopped, if it is running.
- restart
- Causes named to be killed and restarted.
Arguments to named are not preserved by restart, or known by start.
Some mechanism for controlling the parameters and environment should exist.
Implemented as a sh(1)
script.
Paul Vixie (Internet Software Consortium)
named(8)
, named.reload(8)
, named.restart(8)
.
Table of Contents