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

[Nick van den Heuvel]

To my information, nameservers indeed wait till they get a notify that a new zonefile is ready.

Regards,
Nick

Met vriendelijke groet,

Nick van den Heuvel
Test analist

SIDN | Utrechtseweg 310 | 6802 EA | Postbus 5022 | 6802 EA | ARNHEM
T +31 (0)26 352 55 93 | F +31 (0)26 352 55 05 | jabber: nick.vandenheuvel at jabber.sidn.nl
nick.vandenheuvel at sidn.nl | www.sidn.nl


SIDN heeft een nieuw domein! Vanaf 31 oktober zijn wij gevestigd op een nieuw adres: 
Meander 501, 6825 MD Arnhem. 
Het postadres en de telefoonnummers blijven ongewijzigd.

SIDN has a new domain! From 31 October, our office address will be:
Meander 501, 6825 MD Arnhem, The Netherlands. 
Our postal address and phone numbers remain unchanged.



-----Original Message-----
From: opendnssec-develop-bounces at lists.opendnssec.org [mailto:opendnssec-develop-bounces at lists.opendnssec.org] On Behalf Of John Dickinson
Sent: woensdag 19 oktober 2011 16:50
To: opendnssec-develop at lists.opendnssec.org
Subject: Re: [Opendnssec-develop] A NotifyCommand script blocks, what to do?

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.

John 
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,
Wallingford,
Oxfordshire,
OX10 8BA,
U.K.

+44 (0)1491 834957

_______________________________________________
Opendnssec-develop mailing list
Opendnssec-develop at lists.opendnssec.org
https://lists.opendnssec.org/mailman/listinfo/opendnssec-develop