Thanks for this. I just checked, and the bug is fixed in later versions
of dnsmasq. (I didn't determine exactly which one, but I expect it was
around 2.67, when DNSSEC validation was added, and the whole code
handling DNSSEC flag bits was re-written.)
Therefore in the next release of Debian, this
Package: dnsmasq
Version: 2.62-3+deb7u1
Severity: normal
Tags: upstream
Dear Maintainer,
* What led up to the situation?
Asking dnsmasq for a domain/hostname with the "AD" flag set results
in a response with the AD flag, if the response comes from the cache.
* What exactly did you do (or
2 matches
Mail list logo
