Cloudflare over DOT showing Singapore on DNS tests

[Luboknok]

Using the DNS Privacy feature of Merlin my ac86u set to Cloudflare servers 1.1.1.1 and 1.0.0.1.

IPleaks reports both a Singapore IP and DNS address, I am in the USA. Otherwise the connection seems to work. Is this expected?

edit: tested on https://www.dnsleaktest.com/ and it reports the same IP but reports USA.

 

[skeal]

Using the DNS Privacy feature of Merlin my ac86u set to Cloudflare servers 1.1.1.1 and 1.0.0.1.

IPleaks reports both a Singapore IP and DNS address, I am in the USA. Otherwise the connection seems to work. Is this expected?

Cloudflare has been having problems in the USA.

 

[SomeWhereOverTheRainBow]

my "USA" servers are reporting properly.

Using the DNS Privacy feature of Merlin my ac86u set to Cloudflare servers 1.1.1.1 and 1.0.0.1.

IPleaks reports both a Singapore IP and DNS address, I am in the USA. Otherwise the connection seems to work. Is this expected?

edit: tested on https://www.dnsleaktest.com/ and it reports the same IP but reports USA.

are you sure your browser hasn't hijacked your DNS traffic?

 

[Luboknok]

my "USA" servers are reporting properly.


are you sure your browser hasn't hijacked your DNS traffic?

Yes, even a sandboxed fresh profile firefox reports Singapore.

dnsleaktest.com shows USA

Strange

 

[SomeWhereOverTheRainBow]

Yes, even a sandboxed fresh profile firefox reports Singapore.

View attachment 20616

dnsleaktest.com shows USA

View attachment 20617

Strange

are you using a torr browser? because your IP address is reported out of singapore too.

 

[Luboknok]

It turns out it's the VPNs DNS showing Singapore, even when DNS Privacy is activated with Cloudflare. I thought DNS Privacy would override pushed DNS. If not, what's the point?

 

[Swistheater]

It turns out it's the VPNs DNS showing Singapore, even when DNS Privacy is activated with Cloudflare. I thought DNS Privacy would override pushed DNS. If not, what's the point?

you can override VPN dns by nat rules.

iptables -t nat -D PREROUTING -i tun_example -p udp ! --source 192.168.1.1 ! --destination 192.168.1.1 --dport 53 -j DNAT --to 192.168.1.1 2>/dev/null
iptables -t nat -D PREROUTING -i tun_example -p tcp ! --source 192.168.1.1 ! --destination 192.168.1.1 --dport 53 -j DNAT --to 192.168.1.1 2>/dev/null
iptables -t nat -A PREROUTING -i tun_example -p udp ! --source 192.168.1.1 ! --destination 192.168.1.1 --dport 53 -j DNAT --to 192.168.1.1
iptables -t nat -A PREROUTING -i tun_example -p tcp ! --source 192.168.1.1 ! --destination 192.168.1.1 --dport 53 -j DNAT --to 192.168.1.1

if you know which tun interface your vpn is using. you would replace tun_example with that.

or if you want to go by IP range of your vpn interface you can do it by that as well instead of doing it by interface.

there are alot of fun things you can do to control flow of traffic with nat rules.