Issues resolving using as a bind forwarder with DNSSEC enabled


I’m not sure if it’s an issue with or their DNS setup. I can resolve it just fine with DNSSEC enabled when I don’t have a forwarder configured in bind.

I’ve been using as a forwarder for weeks now and this is the first domain that I’ve noticed a problem with.


They seem to have CNAME in the zone apex. That’s against RFCs and it causes problems especially in more complex cases like forwarding. EDIT: to be clear, I do not know what exactly is causing the problem, but I’ve learned to just ignore debugging domains that clearly break standards…


It’s just really strange that it resolves using dig directly asking with the +dnssec flag, but doesn’t when it’s a bind forwarder.

I’m not seeing the same issue with other domains, whether they’re signed or not.


That’s common. The ambiguity caused by apex CNAMEs cause worse trouble when forwarding than with iterating. That’s related to the forwarder returning the whole CNAME chain. Therefore the forwarding resolver can’t e.g. get DNSKEY for the zone apex, as it always gets answer for CNAME’s target instead.