BE550 IPv6 DNS Leak: ISP Servers Override Custom Settings
Hi all,
I’m running an Archer BE550 (v1.0, BE9300 firmware) with AdGuard’s Encrypted DNS. IPv4 DNS override works perfectly, but IPv6 DNS keeps leaking to my ISP’s resolvers, even when I manually set AdGuard IPv6 DNS servers in the router. It's not just that it leaks - it will work as intended for a few moments but then fails entirely, passing all DNS to my ISP and not encrypting any DNS traffic. My guess is that my ISP is constantly rotating IPv6 assignments and so it just keeps messing up my DNS settings? I am not a network guy so I may be getting lost here.
What I’ve tried:
- Disabled “Get IPv6 DNS from ISP” in settings.
-
Manually set AdGuard IPv6 DNS
-
RA/DHCPv6 set to Managed mode with custom DNS.
-
Tested across multiple devices (Windows, mobile) - all leak IPv6 DNS queries to ISP.
-
Verified with
Get-DnsClientServerAddress
in PowerShell and DNS leak test sites. -
Also tested using AdGuard's diagnostic test page - it will indicate encrupted DNS-over-TLS for IPv6 for a few minutes and then fail, as indicated above.
-
Disabling IPv6 entirely stops the leak (all DNS then routes through AdGuard IPv4).
Firmware:
-
Current version: 1.1.2 Build 20250317 rel.18331(5553)
-
Newest firmware changelog mentions a fix for Static IPv6 mode default route loss (Bug #5 in latest update), but static IPv6 is not an option available to me per ISP
I am aware Firmware version 1.1.3 Build 20250421 rel.24697 is released - everytime I try to update through the UI, it says unable to connect to cloud server. Not an issue I am trying to address here and I will attempt a manual firmware update to 1.1.3 only if recommended by the TP-Link folks as a potential fix to the below issues.
Questions for TP-Link / community:
-
Is there a known issue where DHCPv6 mode ignores custom IPv6 DNS settings?
-
Is there a way to completely block ISP-provided IPv6 DNS in RA/DHCPv6 announcements?
If others can test this on BE550 / BE9300 models, or have experience with any of this, please let me know. :-) This will help confirm whether it’s firmware-wide or just my setup.