extra CNAME resolutions in chain
wouter at nlnetlabs.nl
Mon May 29 11:51:01 UTC 2017
On 29/05/17 07:12, Philip O'Sullivan via Unbound-users wrote:
> I'm seeing unbound making extra resolution requests for CNAME records in
> a chain where the domains differ between the record in the question and
> the CNAMEs in the answer. For example a query coming into unbound for a
> host like a.b.c.com <http://a.b.c.com> that gets a reponse from the
> server with CNAME a.b.e.com <http://a.b.e.com>, CNAME, a.d.e.com
> <http://a.d.e.com>, A 184.108.40.206. Instead of returning those immediately
> to the client unbound proceeds to resolve a.b.e.com <http://a.b.e.com>
> and a.c.e.com <http://a.c.e.com>, and then return to the client. From
> the logs, when verbose logging is turned on we see messages like:
> info: sanitize: removing extraneous answer RRset: a.b.e.com
> <http://a.b.e.com>. CNAME IN
> Our unbound config is fairly simple with a forward-zone for "." pointing
> to our upstream DNS servers. We don't have DNSSEC enabled.
> From a quick look at the source I think this is happening in the
> scrubber at
> I was wondering if there was anyway to stop these extra lookups?
There is no way to turn that feature off. The lookups are for defense
against (Kaminsky) cache poisoning scenarios.
On unbound.net there is
http://unbound.net/documentation/patch_announce102.html that describes
this. Also described in (expired draft):
Best regards, Wouter
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 819 bytes
Desc: OpenPGP digital signature
More information about the Unbound-users