[nsd-users] reloading NSD zone configuration

W.C.A. Wijngaards wouter at NLnetLabs.nl
Fri Feb 11 13:20:24 CET 2011


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

On 02/01/2011 08:37 AM, Jan-Piet Mens wrote:
zone changes are a common feature request.

> Alternatively, can you confirm that a safe procedure for adding or
> removing zones in nsd.conf remains as so:
> 
> 1. Add/remove zone definitions from nsd.conf
> 2. nsdc rebuild
> 3. nsdc restart
> 
> I note that a `rebuild' signals a running NSD, but we've experienced
> "can't bind udp socket: Address already in use" messages when doing so,
> whereupon the server doesn't start up: "server initialization failed,
> nsd could not be started". (NSD version 3.2.7.)
> 
> Will a rebuild also "patch", in other words, will it merge changes
> received during AXFR/IXFR?

No, rebuild does not do that, for that you need to run nsdc patch, or
nsd-patch (nsdc patch also signals a reload to the running server).

If you add a secondary zone, you can issue the restart without the
rebuild, just provide an empty zonefile, and it starts a zonetransfer.

Best regards,
   Wouter
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/

iEYEARECAAYFAk1VKYgACgkQkDLqNwOhpPjEBQCdFz5Vi1eeSkGa1rU/qAnvjy6U
Iq4AnRV/zByOwkcekE3ygV/2UyZlx8SE
=cMIy
-----END PGP SIGNATURE-----


More information about the nsd-users mailing list