[Opendnssec-develop] A NotifyCommand script blocks, what to do?

John Dickinson jad at sinodun.com
Wed Oct 19 14:49:42 UTC 2011

What do name servers do? Do they really wait for the notify response or do they get on with better things and let the secondary decide if and when it will get the xfr?

How about it tries a few (5?) times and then carries on.

On 19 Oct 2011, at 15:14, Yuri Schaeffer wrote:

>> Is this what we want (let the worker wait until the notify command is
>> terminated)? Or do we want the signer daemon to fork off the notify
>> command script and continue its process regardless of the result of the
>> notify command script? In the latter case, you will get fresh signed
>> zone files, but we don't know if they are ever picked up by the name server.
> Neither sound very compelling, although I'm unsure what you currently do when a notify fails.
> Would it be possible to fork off the script and let the fork schedule a task upon completion for a worker to pickup, read and act upon the status?
> Having the workers block for a long time does not seem to be a good idea to me.
> //yuri
> _______________________________________________
> Opendnssec-develop mailing list
> Opendnssec-develop at lists.opendnssec.org
> https://lists.opendnssec.org/mailman/listinfo/opendnssec-develop

jad at sinodun.com
Sinodun Internet Technologies Ltd.
Stables 4, Suite 11,
Howbery Park,
OX10 8BA,

+44 (0)1491 834957

More information about the Opendnssec-develop mailing list