MT6000 DNS Leak with AGH and WG VPN

I tried scouring the forums but I havent seen any fixes.

Router: MT6000
Firmware: 4.7.0 OP24
Description:
Im using WireGuard config from Windscribe with Global Proxy. My Adguardhome on the other hand, has my preferred DOH servers from Cloudflare, Google, and Quad9 with proper fall back addresses. Now, when I turn off the VPN and use AGH only, the DNS leak doesnt happen and when VPN is enabled, it does. I tried toggling AGH handle client request on and off but its the same result.

VPN On (Rise Asia Technology Limited is my providers DNS)

However, that address doesnt appear at all when VPN is off.

I think I got the fix?

Apparently using Quad9's DOH and DOT causes the leak. I tried commenting it out and did the tests again with Cloudflare and Google DOH and DOT active (parallel requests and optimistic caching enabled), the leak never happened again.

Upstream DNS:

https://dns.cloudflare.com/dns-query
#https://dns.quad9.net/dns-query
https://dns.google/dns-query
tls://one.one.one.one
#tls://dns.quad9.net
tls://dns.google

Hi,
This is the first time I have seen this.

I guess the network in your area may have hijacked the Quad9 domain name.

Perhaps you can try to manually resolve the nord9 domain name and use the obtained IP address to query the geographic location information for verification.

Really weird right? And this will only happen when VPN is turned on. AGH as standalone doesn't have any problems with it.

I will your proposed testing later.

This is the only info that I could find.

Config: VPN Off
dig / dnslookup returns:

root@GL-MT6000:~# nslookup dns.quad9.net
Server:         121.54.70.162
Address:        121.54.70.162:53

Non-authoritative answer:
Name:   dns.quad9.net
Address: 149.112.112.112
Name:   dns.quad9.net
Address: 9.9.9.9

Non-authoritative answer:
Name:   dns.quad9.net
Address: 2620:fe::fe
Name:   dns.quad9.net
Address: 2620:fe::9
root@GL-MT6000:~# dig dns.quad9.net +short
149.112.112.112
9.9.9.9

Config VPN On:

root@GL-MT6000:~# dig dns.quad9.net +short
;; communications error to 121.54.70.162#53: timed out
;; communications error to 121.54.70.162#53: timed out
;; communications error to 121.54.70.162#53: timed out
;; communications error to 121.54.70.154#53: timed out

So 121.54.70.154#53 is obviously not a Quad9 address. When I tried to check it via ipinfo.io, it returns:

Which is my Internet Provider's Prepaid / Cell telecom company. Im using Postpaid Fiber which is handled by their sister company, PLDT, but its highly possible that theyre sharing the same infra. I could simply not use Quad9 as a resolver for now since VPN is much more important but its a waste since Quad9's response time is better than Cloudflare or Google most of the time. Any possible lead from this info?

Hi,

It seems that the DNS address sent by the ISP following the DHCP does not support the resolution of Quad9. You can manually add the DNS address for your upstream interface, as shown in the picture below.

This may help you solve this issue.

1 Like

I can confirm that this fixed the issue. Thanks!