[nsd-users] nsd-notify retries?

Paul Wouters paul at xelerance.com
Mon Nov 28 16:17:51 UTC 2011

On Mon, 28 Nov 2011, W.C.A. Wijngaards wrote:

> In NSD3, the daemon can perform notifies (with retries) for you, all in
> parallel.  This only happens when you have notify: configured for the
> zone(s) and the serial number is updated (i.e. you nsdc rebuild && nsdc
> reload, or it is a slave zone and the master is updated).

But when adding a zone, you need a restart, not just rebuild & reload
What happens then?

> In NSD4, the same thing, but nsdc is obsolete, you have nsd-control
> notify, nsd-control contacts the server over SSL and the daemon sends
> notifies for one or all zones.

Good, so on startup will it send notifies to all secondaries per default?
eg this could then be removed from the init scripts?

the 50 at a time is fine when it is the daemon doing it, meaning the server
is up and running. The issue with nsd3 is that you have to run nsd-notify
before the daemon launches, meaning you are down while waiting.


More information about the nsd-users mailing list