@merlin @stefan @mmeier
DNS resolution happens in the order sent by your DHCP server, unless there's a client-side option to change that. So if you don't want to mess with the clients config, either put the IPv6 DNS at the top of the DHCP response, or simply remove the IPv4 address.
Conversation
Notices
-
Embed this notice
Mauricio Teixeira 🇧🇷🇺🇲 (badnetmask@hachyderm.io)'s status on Monday, 18-Nov-2024 12:35:41 JST Mauricio Teixeira 🇧🇷🇺🇲 -
Embed this notice
Merlin.2160p.BDRip.x265.10bit (merlin@toot.kif.rocks)'s status on Monday, 18-Nov-2024 12:35:43 JST Merlin.2160p.BDRip.x265.10bit @stefan I don’t have any issues, everything is working (I just don’t like the stats in AdGuard Home). Removing DNS from my DHCPv4 feels like a hack though. But everything should support IPv6 so I might end up trying that
-
Embed this notice
Stefan :veritrek: (stefan@social.stefanberger.net)'s status on Monday, 18-Nov-2024 12:35:44 JST Stefan :veritrek: @merlin hm I think there is no priority at least. You could disable or block DNS on IPv4 on your network.
Do you have any issues? -
Embed this notice
Merlin.2160p.BDRip.x265.10bit (merlin@toot.kif.rocks)'s status on Monday, 18-Nov-2024 12:35:46 JST Merlin.2160p.BDRip.x265.10bit IPv6 experts: most devices in my home network still do their DNS lookups via the DHCP-provided IPv4 DNS server address rather than the ND IPv6 address. Is this because the IPv4 address are both in 10.0.0.0/8 and the IPv6 spans from the client (GUA) to the DNS server (ULA)?
-
Embed this notice