Maintained by: NLnet Labs

[Unbound-users] Strange result from Unbound cache

W.C.A. Wijngaards
Tue Nov 30 16:20:28 CET 2010


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

On 11/26/2010 10:40 AM, lst_hoe02 at kwsoft.de wrote:
>>> Yes, but i'm a little bit baffled that identical records are returned.
>>> Does unbound cache it this way or are the records subtil different?
>>
>> Unbound just returns what the authoritative nameserver sent.

Yes.  It caches what the authority server sends.  For speed reasons it
does not (try to) remove duplicates.  Except in special corner cases
where it does remove duplicates (where it tries to make sense of RRSIGs
that are in the wrong section of the message, and when it thus adjusts
the message it removes duplicates).

>> BIND removes duplicate nameserver addresses from responses, it seems.

Unbound does not introduce duplicates itself, but also does not remove
them if the authority server sends them like that.

Unbound preserves the exact order of the records as well.

> As it does not hurt i will simply ignore it further on.
> 
> Thanks for your input
> 
> Andreas

Best regards,
   Wouter
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAkz1FjwACgkQkDLqNwOhpPiwAACZAeG7c4l5BLWefW49rO0R/SRb
C/UAn1r3SwCP9/PeuJcSFzE7INtm067K
=vsV7
-----END PGP SIGNATURE-----