is the shell script that used to control nsd(8) and zonec(8) from
is also suitable to be linked into
like systems for automatic startup of nsd(8) at boot time.
At every invokation,
will try to read the nsd.conf(5) configuration file. An example of
such configuration file is distributed with the
The config file is checked for errors before it is used, see
Initiate nsd(8) name space database reload by sending
Rebuild the nsd(8) database by invoking zonec(8) with appropriate
Restart nsdc(8). This equals to nsdc stop && nsdc start.
Check whether nsd(8) is running. Returns error message and error
code if it is not running, and no message and zero error code
Updates all the slave zones which have
from localhost (127.0.0.1 or ::1) allowed.
If a TSIG key is specified for the allow-notify statement in the
config file, it will be used to secure the notify. Note that NSD
keeps track of zone timeouts automatically, this is only needed if
you want to manually force updates by sending notify messages to the
Another method you can use is to stop nsd, delete the xfrd.state
file and then start nsd again. It will try to update all zones.
This method does not require allow-notify: statements.
Sends notify messages to all the slaves for all the zones that have the
keyword in the
file. If a TSIG key is specified for a notify statement, it will be
used to secure the notification message to that slave server.
Merge zone transfer changes back to zone files. It reads in the nsd
database (nsd.db) and difffile (ixfr.db), and overwrites the zone
text files if they have been updated. Running this regularly
ensures that the difffile does not grow infinitely.
Specify configfile to use instead of the default
Configuration file for nsd to change default pathnames and
flags. The zone names, pathnames to zone files and access control
lists are also in nsd.conf(5).
Lockfile for the
database access by operator tools.
Journal of zone transfers, the diff file containing the new zone
State for the zone transfer process of
Contains timeouts for the zones and whether zones are expired.
the process id of the name server.
will return zero return code if operation was successful and
an error message to standard output plus a non-zero return code
was written by NLnet Labs and RIPE NCC joint team. Please see
CREDITS file in the distribution for further details.
Syntax checking of the config file is rudimentary and error
messages may be wrong. If you do a nsdc patch, whilst a (long) zone
transfer is busy, the zone transfer contents will be partially
lost. After a reload, this will be detected and the zone transfer
should be restarted. The reload that happens at the end of nsdc
patch also frees up memory churn in
caused by zone transfers.