1 Upgrading from NSD 3.x to NSD 4 2 3 by Wouter C.A. Wijngaards, NLnetLabs, Jul 2012 4 5 This document lists the changes in the upgrade from NSD 3 to NSD 4 systems. 6 (scroll down for the NSD 2.x to NSD 3 upgrade manual). 7 8 * nsdc is gone. You can control the daemon via kill -HUP and kill -TERM, 9 or you can use nsd-control. 10 11 * to setup nsd-control you have to run nsd-control-setup (as root) and enable 12 remote-control in the nsd.conf file. It uses SSL to contact the daemon. 13 14 * the nsd.conf file from NSD3 can be used for NSD4 (defaults for new stuff). 15 * the difffile: setting is no longer used but ignored for 16 backwards compatibility. 17 * zones listed in nsd.conf are served. 18 * the zonelistfile: setting sets the file where zones that are 19 added dynamically (and can be removed dynamically) are stored. 20 * the xfrdir: is used to store temporary zone transfer files. 21 * it is possible to define patterns in the nsd.conf file and 22 use the patterns to give config settings for the zones. 23 * patterns accept the same sort of settings which NSD3-zones did. 24 * you can make super-patterns with the include-pattern: setting 25 * the zonefile: statement creates directories when needed, if they 26 do not exist. In the zonefile: statement you can use %s (and 27 other codes) to use (part of) the name of the zone to generate 28 the pathname of the zonefile. 29 * if there is no zonefile (for slave zones) it is not used. 30 31 * nsdc rebuild and so on is gone, use nsd-control reload or kill -HUP. 32 * it scans if zonefiles are modified and reads those. 33 * you can also specify a zone by name and have nsd read that file. 34 * if you nsd-control reconfig it rereads the config file for zones. 35 * nsdc patch is not necessary 36 * the database is edited at runtime. 37 * it mmap's the nsd.db file for file I/O, this increases 38 virtual memory usage of NSD with the size of the file. 39 * if you like cronjobs, you could have one to nsd-control write 40 and write slave zones that have changed to their zonefile. 41 * other nsdc commands, reconfig (reread patterns, zones, keys), 42 add a zone, delete a zone, and zone transfer control, statistics. 43 44 45 46 Upgrading from NSD 2.x to NSD 3 47 48 by Wouter C.A. Wijngaards, NLnetLabs, Aug 2006 49 50 This document lists the changes in the upgrade from NSD 2 to NSD 3 systems. 51 52 * The nsdc.conf file is gone. 53 * specify the config file to nsdc by using the -c <file> option. 54 * binaries are searched for in the installation bin directory, 55 in the PATH and in the directory of nsdc.sh itself. 56 * other options go into the new nsd.conf file. 57 58 * The nsd.masters file is gone, replaced by nsd.conf. 59 * Look at nsd.conf.5 manual page to see format. 60 * you can list nsd-commandline-options, zones, masters, slaves, keys. 61 * TSIG support: please list the TSIG keys in nsd.conf, or do this with 62 include: "keys.conf" and provide additional security for that file. 63 * For every zone include lines: 64 zone: 65 name: "example.com" 66 zonefile: "example.com.txt" 67 * For secondary zones include in the zone entry: 68 request-xfr: <ip of master> <tsig keyname or NOKEY> 69 allow-notify: <same as above> 70 * For master zones include in the zone entry: 71 provide-xfr: <ip of slave> <tsig keyname or NOKEY> 72 notify: <same as above> 73 * NSD does not provide IXFR, so for secondaries that connect to NSD use 74 request-xfr: AXFR <ip> <key> that will only use AXFR, not IXFR to 75 request zone transfers. 76 77 * No more need for a cron job to do a nsdc update. 78 * nsd will update automatically all secondary zones from master. 79 * You should never need to do nsdc update or nsdc notify by hand. 80 * You can still use a cronjob to do nsdc patch. 81 nsdc patch moves the zone transfer content from temporary storage 82 to the zone files, recompiles the database and reloads nsd. 83 84
Indexes created Wed Mar 04 05:31:52 UTC 2026