Maintained by: NLnet Labs

[Unbound-users] Does not cache DNAME ?

Stephane Bortzmeyer
Wed Mar 23 17:17:28 CET 2011


When I query repeatedly a name which is covered by a DNAME, the TTL in
the answer makes me thing Unbound does not cache it:

% dig -x 128.232.233.1
...
233.232.128.in-addr.arpa. 86400 IN      DNAME   233.232.128.in-addr.arpa.cam.ac.uk.

% dig -x 128.232.233.1
...
233.232.128.in-addr.arpa. 86400 IN      DNAME   233.232.128.in-addr.arpa.cam.ac.uk.

While BIND has the expected behaviour:

% dig -x 128.232.233.1
...
233.232.128.in-addr.arpa. 86180 IN      DNAME   233.232.128.in-addr.arpa.cam.ac.uk.

% dig -x 128.232.233.1
...
233.232.128.in-addr.arpa. 86168 IN      DNAME   233.232.128.in-addr.arpa.cam.ac.uk.

Unbound 1.4.6