[Dnsmasq-discuss] NXDOMAIN is sent instead of NODATA when querying for non-existent AAAA records

Simon Kelley simon at thekelleys.org.uk
Thu Aug 5 14:50:23 UTC 2021

There's lots of code in dnsmasq which tries to get this right.


forward AAAA upstream
upstream replies with NXDOMAIN
dnsmasq checks if it knows data for other record types like A and if so
rewrites NXDOMAIN to NODATA.

TLDR; We though of this, and we think it works correctly. If you've
found a specific case where it isn't working, we'll need more
information on exactly what that case is, and what version of dnsmasq
you're running.

Setting --log-queries, demonstrating the problem, then sending the logs,
would be a good start.



On 04/08/2021 20:42, Wojtek Swiatek wrote:
> Hello everyone
> I noticed that my dnsmasq server is sending an NXDOMAIN instead of
> a NODATA when I query it for AAAA records it does not have.
> This is, I believe, not the correct behaviour
> (https://datatracker.ietf.org/doc/html/rfc2308
> <https://datatracker.ietf.org/doc/html/rfc2308> - see 1 Terminology →
> NODATA) and that response breaks queries that otherwise would have tried
> the A record. See for
> instance https://kc.mcafee.com/corporate/index?page=content&id=KB73433&actp=LIST
> <https://kc.mcafee.com/corporate/index?page=content&id=KB73433&actp=LIST>
> As a workaround: is there a way to automatically populate AAAA
> records together with the A ones (from DHCP)?
> _______________________________________________
> Dnsmasq-discuss mailing list
> Dnsmasq-discuss at lists.thekelleys.org.uk
> https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss

More information about the Dnsmasq-discuss mailing list