Custom IPv6 DNS not respected, uses Google DNS instead
Hello TP-Community,
My Synology Router died so I decided to come back to TP-Link and have a AX6000. As I did previously, I'm running a pi-hole on another device, but on a different subnet due to my ISP provided home gateway/router. My home gateway itself does not allow me to specify an alternate DNS, which is one of the reasons I have my own router.
Setting a primary and secondary DNS under IPv4 works as expected. The IP address of my pi-hole device is provided. However, when setting the primary and secondary under IPv6, I do not see the same or expected behavior. Only 1 of my IPv6 addresses is set and the router instead provides a public Google DNS IPv6 address. I currently have both primary and secondary filled in, and even when 1 is filled in, Google's DNS address is provided to my clients. The order of Google's DNS address is even changed when I'm only using the secondary address, so my router is clearly doing this.
TP-Link Settings:
PC network details, all retrieved automatically:
In searching the forum, I have found 2 cases where it seems like the same thing is happening.
With Deco:
https://community.tp-link.com/en/home/forum/topic/500008
And on the business side:
https://community.tp-link.com/en/business/forum/topic/619772
I would really like some help in resolving this issue! Thanks in advance!
Hi,
That is an interesting observation!
It appears to be common on TP-Link routers, as I am also seeing this behavior on mine.
If there is only one IPv6 DNS server provided (be it via assignment by the ISP or by manually entering the same IP address twice), then the router seems to substitute 2001:4860:4860::8844 as the secondary DNS server, even though it is not shown like that in the router's web interface.
The only workaround I found is to manually enter two different IPv6 addresses in the DNS server fields, the second one being either that of a real DNS server or a bogus IPv6 address, like shown in the screenshot below.
Hi,
That is an interesting observation!
It appears to be common on TP-Link routers, as I am also seeing this behavior on mine.
If there is only one IPv6 DNS server provided (be it via assignment by the ISP or by manually entering the same IP address twice), then the router seems to substitute 2001:4860:4860::8844 as the secondary DNS server, even though it is not shown like that in the router's web interface.
The only workaround I found is to manually enter two different IPv6 addresses in the DNS server fields, the second one being either that of a real DNS server or a bogus IPv6 address, like shown in the screenshot below.