IPV6 queries from different local devices go through, can the AAAA queries be disabled?

I noticed that 4.2% of the queries are IPV6. I'm wondering why is that, because all my local devices (including iot devices) are configured with IPV4.


All Amazon devices, Samsung TV, Smartthings hub, Wyze camera, ipads, Windows PCs, they query for some domains in IPV6. A lot of them are cached but in most cases the reply is NODATA.
It bothers me to see that when IPV6 queries should not be asked

What you see is normal.

Those are requests for AAAA records - your log doesn't detail whether a client did issue a request via IPv4 or IPv6, but given that the Client shows up as hostname, it would be likely by that client's IPv4. Note that the DNS protocol itself is indifferent to the transport protocol used, i.e. a DNS reply would be the exact same regardless.

It is not unusual for clients to request both A and AAAA records for a given domain.

All local clients have hostnames.home because I specifically gave them those names on the router as DHCP reservation. I like that because with Conditional forwarding Pi-hole identifies correctly my clients. My router has IPV6 disabled. And yes clients are configure with IPV4 addresses.
But I'm sorry I still don't understand the IPV6 explanation. Did you mean that an IPV4 client can issue a query for an AAAA record and the DNS replies with that AAAA record? But most of the replies are NODATA

Yes.

That means there is no AAAA record for that domain.

1 Like

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.