[nsd-users] nsd 3.2.9 released

Olafur Gudmundsson ogud at ogud.com
Mon Nov 28 14:02:16 UTC 2011

On 28/11/2011 05:31, Peter Koch wrote:
> On Mon, Nov 28, 2011 at 10:09:20AM +0100, Matthijs Mekking wrote:
>> We want to prevent fragmentation as much as possible. Optional
>> information should not be able to cause fragmentation.
> not everything in the additional section is 'optional', think of
> additional data originating from glue records.
>> Still, IP packets fragmented by the kernel may still cause problems
>> across the network. One example is that a box is not considering one
>> fragment as a DNS packet and it may be drop the packet.
> True, but I am not convinced that pleasing this brokenness by
> suggesting fragments are avoidable (and thus making those that aren't
> even more exceptional) is the right way to go.  Race towards
> lowest standards applies.

While in practice I have no problem with suppressing the zone's NS set 
from most answers this has unindented side effects.
For most old resolver this changes their affinity from the Child side NS 
set to the parent one (i.e. makes them Parent centric).

If more an more authoritative servers do this we should be strongly 
recommending that resolvers fetch the child NS set once the resolver 
discovers a delegation.


More information about the nsd-users mailing list