1NSDC(8) NSDC 3.2.8 NSDC(8)
2
6 nsdc - Name Server Daemon (NSD) control script.
7
9 nsdc [-c configfile] start | stop | reload | rebuild | restart | run‐
10 ning | update | notify | patch
11
13 Nsdc is the shell script that used to control nsd(8) and zonec(8) from
14 NSD distribution. Nsdc is also suitable to be linked into /etc/rc.d
15 directory on BSD like systems for automatic startup of nsd(8) at boot
16 time.
17 At every invokation, nsdc will try to read the nsd.conf(5) configura‐
19 tion file. An example of such configuration file is distributed with
20 the NSD package as nsd.conf.sample. The config file is checked for
21 errors before it is used, see nsd-checkconf(8).
22 Possible nsdc applications are:
24 start Start nsd(8).
26 stop Shut down nsd(8) by sending SIGTERM to it.
28 reload Initiate nsd(8) name space database reload by sending SIGHUP.
30 rebuild
32 Rebuild the nsd(8) database by invoking zonec(8) with appropri‐
33 ate arguments.
34 restart
36 Restart nsdc(8). This equals to nsdc stop && nsdc start.
37 running
39 Check whether nsd(8) is running. Returns error message and error
40 code if it is not running, and no message and zero error code
41 otherwise.
42 update Updates all the slave zones which have allow-notify: from local‐
44 host (127.0.0.1 or ::1) allowed. If a TSIG key is specified for
45 the allow-notify statement in the config file, it will be used
46 to secure the notify. Note that NSD keeps track of zone timeouts
47 automatically, this is only needed if you want to manually force
48 updates by sending notify messages to the localhost.
49 Another method you can use is to stop nsd, delete the xfrd.state
51 file and then start nsd again. It will try to update all zones.
52 This method does not require allow-notify: statements.
53 notify Sends notify messages to all the slaves for all the zones that
55 have the notify: keyword in the nsd.conf file. If a TSIG key is
56 specified for a notify statement, it will be used to secure the
57 notification message to that slave server.
58 patch Merge zone transfer changes back to zone files. It reads in the
60 nsd database (nsd.db) and difffile (ixfr.db), and overwrites the
61 zone text files if they have been updated. Running this regu‐
62 larly ensures that the difffile does not grow infinitely. If any
63 zone text files have been changed (including those of the master
64 zones), the nsd.db is rebuild and nsd is reloaded.
65
67 -c configfile
68 Specify configfile to use instead of the default
69 /etc/nsd/nsd.conf.
70
72 /etc/nsd/nsd.conf
73 Configuration file for nsd to change default pathnames and NSD
74 flags. The zone names, pathnames to zone files and access con‐
75 trol lists are also in nsd.conf(5).
76 /var/lib/nsd/nsd.db
78 default NSD database
79 /var/lib/nsd/nsd.db.lock
81 Lockfile for the NSD database access by operator tools.
82 /var/lib/nsd/ixfr.db
84 Journal of zone transfers, the diff file containing the new zone
85 contents transferred.
86 /var/lib/nsd/ixfr.state
88 State for the zone transfer process of NSD. Contains timeouts
89 for the zones and whether zones are expired.
90 /var/run/nsd/nsd.pid
92 the process id of the name server.
93
95 Nsdc will return zero return code if operation was successful and an
96 error message to standard output plus a non-zero return code otherwise.
97
99 nsd(8), nsd.conf(5), nsd-checkconf(8), nsd-notify(8), nsd-patch(8),
100 nsd-xfer(8), zonec(8)
101
103 NSD was written by NLnet Labs and RIPE NCC joint team. Please see CRED‐
104 ITS file in the distribution for further details.
105
107 Syntax checking of the config file is rudimentary and error messages
108 may be wrong. If you do a nsdc patch, whilst a (long) zone transfer is
109 busy, the zone transfer contents will be partially lost. After a
110 reload, this will be detected and the zone transfer should be
111 restarted. The reload that happens at the end of nsdc patch also frees
112 up memory churn in NSD caused by zone transfers.
113NLnet Labs Mar 22, 2011 NSDC(8)