Handling of zone transfers and notify messages

Robert E.Seastrom rs at seastrom.com
Mon Oct 18 15:28:54 UTC 2004

Miek Gieben <miekg at atoom.net> writes:

> [On 18 Oct, @ 14:59, Måns wrote in "Re: Handling of zone transfers ..."]
>> > Is this not the desired behavior? Or am I missing something (obvious)?
> <SNIP explanation>
>> On top of this comes the issue what should be done with failed zones.
>> Several outcomes are possible, as has been mentioned above; 
>> 1. go SERVFAIL, ie. remove zone.
>> 2. go lame, ie. remove AA but serve and refuse AXFR. (BIND method up to
>> expiry.)
>> 3. hand out old data with AA bit set and pretend it is raining. 
>> Nos 1 and 2 are probably more clever than 3. In effect, #3 is what is being
>> done today, with all the other zones in that particular nsd instance --
>> hence the SLA issues. 
>> Clearer? 
> yes, very much so, thanks.
> About the 3 points you mention. #2 is rather hard to do for an
> authoritative only server... :)

How so?  It's just a bit in the reply, you serve the data, but don't
claim to be authoritative.

> So IMO that only leaves #1, as people have been doing with wrapper
> scripts. I will look into it,



More information about the nsd-users mailing list