We are looking into it (if only because the question comes up about once a
week now)
It's been a little more than a week since the question last turned up
I'd also like to know if any progress has been made to allow NSD to have
zones added/removed on the fly, somewhat along the lines of BIND's `rndc
addzone/delzone', perhaps?
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?
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.
We are looking into it (if only because the question comes up about once a
week now)
Itās been a little more than a week since the question last turned up
Iād also like to know if any progress has been made to allow NSD to have
zones added/removed on the fly, somewhat along the lines of BINDās `rndc
addzone/delzoneā, perhaps?
Alternatively, can you confirm that a safe procedure for adding or
removing zones in nsd.conf remains as so:
Kristen Eisenberg
Billige FlĆ¼ge
Marketing GmbH
Emanuelstr. 3,
10317 Berlin
Deutschland
Telefon: +49 (33)
5310967
Email:
utebachmeier at
We are looking into it (if only because the question comes up about
once a
week now)
It's been a little more than a week since the question last turned up
And in this time, the plan is to do this in NSD 4.
I'd also like to know if any progress has been made to allow NSD to have
zones added/removed on the fly, somewhat along the lines of BIND's `rndc
addzone/delzone', perhaps?
Well, the implementation of NSD 4 is progressing. And it includes
nsd-control addzone and nsd-control delzone, on the fly addition and
removal of zones.
Alternatively, can you confirm that a safe procedure for adding or
removing zones in nsd.conf remains as so:
