[nsd-users] nsd-notify retries?

Paul Wouters paul at xelerance.com
Mon Nov 28 15:15:15 UTC 2011

On Mon, 28 Nov 2011, Michael Tokarev wrote:

> Now, the questions.
> Should maybe nsd-notify implement the functionality of the
> nsdc script in this case, by scanning the conffile and sending
> all notifies to all found zones and to all nameservers just the
> same way as `nsdc notify' does, but doing it all in parallel, not
> one after another?
> And, should nsd-notify wait for so long and try to do so many
> attempts for each?  Maybe do just two attempts (second within
> a 1-second interval) and be done with it?  Or maybe there should
> be some option for that?
> Or maybe it is better for nsd itself to send the notifies, f.e.
> as triggered by nsd-notify - so that nsd-notify does not send
> notifies itself but sends a trigger to a running daemon who
> maintains list of "pending" notifications?  (Probably too
> complicated for the daemon)
> Why nsd-notify does not detect ICMP errors which are being
> returned by the operating system, and waits till timeout
> expires?

I agree, and have brought this up in the past. I think it has
not been considered a high priority item because the focus of
nsd has been more on small sets of zones like TLDs. When you run
100 zones with nsd and you have a name server outage, all the
notify delays cause significant problems. Or in our case, we always
have some half broken test zones and test servers that are not
working causing massive delays in the init scripts.

I think the nsd team also feels the separate nsd-notify is an
obsolete feature, but I'm not sure if just restarting the daemon
itself causes the built-in notify code to trigger.

I would be happy if nsd-notify provided a "fire and forget" option,
even willing to write the patch :)


More information about the nsd-users mailing list