1nsdc(8) BSD System Manager's Manual nsdc(8)
2
4 nsdc — Name Server Daemon (NSD) Control Script
5
7 nsdc [-c configfile] start | stop | reload | rebuild | restart | running
8 | update | notify | patch
9
11 Nsdc is the shell script that used to control nsd(8) and zonec(8) from
12 NSD distribution. Nsdc is also suitable to be linked into /etc/rc.d
13 directory on BSD like systems for automatic startup of nsd(8) at the boot
14 time.
15 At every invokation nsdc will try to read the nsd.conf(5) configuration
17 file. An example of such configuration file is distributed with the NSD
18 package as nsd.conf.sample. The config file is checked for errors before
19 it is used, see nsd-checkconf(8).
20 -c configfile
22 Specify configfile to use instead of the default
23 /etc/nsd/nsd.conf.
24 Possible nsdc applications are:
26 start Start nsd(8)
28 stop Shut down nsd(8) by sending SIGTERM to it.
30 reload Initiate nsd(8) name space database reload by sending SIGHUP
32 rebuild
34 Rebuild the nsd(8) database by invoking zonec(8) with appropriate
35 arguments.
36 restart
38 Restart nsdc(8) This equals to nsdc stop && nsdc start
39 running
41 Check whether nsd(8) is running. Returns error message and error
42 code if it is not running, and no message and zero error code
43 otherwise.
44 update Updates all the slave zones which have allow-notify: from local‐
46 host (127.0.0.1 or ::1) allowed. If a TSIG key is specified for
47 the allow-notify statement in the config file, it will be used to
48 secure the notify. Note that NSD keeps track of zone timeouts
49 automatically, this is only needed if you want to manually force
50 updates by sending notify messages to the localhost.
51 Another method you can use is to stop nsd, delete the xfrd.state
53 file and then start nsd again. It will try to update all zones.
54 This method does not require allow-notify: statements.
55 notify Sends notify messages to all the slaves for all the zones that
57 have the notify: keyword in the nsd.conf file. If a TSIG key is
58 specified for a notify statement, it will be used to secure the
59 notification message to that slave server.
60
62 /etc/nsd/nsd.conf
63 Configuration file for nsd to change default pathnames and NSD
64 flags. The zone names, pathnames to zone files and access control
65 lists are also in nsd.conf(5).
66 /etc/nsd/nsd.db
68 default NSD database
69 /etc/nsd/nsd.db.lock
71 Lockfile for nsd database access by operator tools.
72 /etc/nsd/ixfr.db
74 Journal of zone transfers, the diff file containing the new zone
75 contents transferred.
76 /etc/nsd/xfrd.state
78 State for the zone transfer process of NSD. Contains timeouts for
79 the zones and whether zones are expired.
80 /var/run/nsd.pid
82 the process id of the name server.
83
85 Nsdc will return zero return code if operation was successful and an
86 error message to standard output plus a non-zero return code otherwise.
87
89 nsd(8), nsd.conf(5), nsd-checkconf(8), nsd-notify(8), nsd-patch(8),
90 nsd-xfer(8), zonec(8)
91
93 NSD was written by NLnet LABS and RIPE NCC joint team. Please see CREDITS
94 file in the distribution for further details.
95
97 Syntax checking of the config file is rudimentary and error messages may
98 be wrong. If you do a nsdc patch, whilst a (long) zone transfer is busy,
99 the zone transfer contents will be partially lost. After a reload, this
100 will be detected and the zone transfer should be restarted. The reload
101 that happens at the end of nsdc patch also frees up memory churn in NSD
102 caused by zone transfers.
103FreeBSD Sep 7, 2007 FreeBSD