man nsdc (Administration système) - nsdc

NAME

nsdc - Name Server Daemon (NSD) Control Script

SYNOPSIS

nsdcstart|stop|reload|rebuild|restart|running|update|notify

DESCRIPTION

Nsdc

is the shell script that used to control nsd() and zonec() from NSD distribution. Nsdc is also suitable to be linked into /etc/rc.d directory on like systems for automatic startup of nsd() at the boot time.

At every invokation nsdc will try to source /etc/nsd/nsdc.conf configuration file (shell script) where default configuration settings can be overwritten. An example of such configuration file is distributed with the NSD package as nsdc.conf.sample

Possible nsdc applications are:

start
Start nsd()
stop
Shut down nsd() by sending to it.
reload
Initiate nsd() name space database reload by sending
rebuild
Rebuild the nsd() database by invoking zonec() with appropriate arguments.
restart
Restart nsdc() This equals to nsdc stop && nsdc start
running
Check whether nsd() is running. Returns error message and error code if it is not running, and no message and zero error code otherwise.
update
Updates all the slave zones which have keyword in nsd.zones file from its masters and invokes and if necessary.
notify
Sends message to all the masters for all the zones that have keyword in nsd.zones file.

See the README file for detailed description of nsd.zones file format.

FILES

/etc/nsd.zones
Default location of configuration file.
/etc/nsd/nsd.db
default NSD database
/var/run/nsd.pid
the process id of the name server.
/etc/nsd/nsdc.conf
Optional configuration file for nsdc to overwrite default pathnames and NSD flags.

DIAGNOSTICS

Nsdc

will return zero return code if operation was successful and an error message to standard output plus a non-zero return code otherwise.

SEE ALSO

nsd(8) ,nsd-notify(8) ,nsd-xfer(8) ,zonec()

AUTHORS

NSD

was written by NLnet LABS and RIPE NCC joint team. Please see CREDITS file in the distribution for further details.

BUGS

nsd.zones

syntax checking is almost nonexistent in nsdc erroneous lines are most likely to be ignored or will produce unexpected results. There is no locking for and operations so those should be used with caution.

update with more than one master will give error messages and wont work with tsig. To fix the problem one can comment out checking for tsig file presence in