DNS leak test showing USA cloudflare addresses instead of local NextDNS?
Hi there, I have been using the service for about a week now and have been enjoying the local fast queries and speeds. When I first got my service up and running I had 2 local dns servers powered by nextdns. Now when I am testing for dns leaks I am seeing entries for Cloudflare addresses back to USA - 172.70.37.108
Being in Aus this creates a noticable difference going from <10ms to ~330ms ping response times. Is this a cause of a setting ticked under the performance section in the settings? Again just seeking some clarity about what is causing this. Thanks.
Edit: I have just performed another leak test, no neither NextDNS servers are showing and am getting multiple Cloudflare addresses. I run a PiHole setup and force all traffic through it using the 2x servers provided under my https://my.nextdns.io/ page.
119 replies
-
I think that this service is used by hundreds of thousands of people and the few that have problems with it are thinking that the service is broken, it doesn't work. Isn't it funny?
Maybe some are expecting NextDNS to come to their house and fix it for them.They are offering instructions, apps, tools, recommendations... If you want to go your way, you should own it, you should know what you are doing.
-
NextDNS said:
Myth0ne when over 300k your configuration is no longer used. It is like using NextDNS with no configuration : 0 filtering, 0 logging, no EDNS, no CNAME folding and so on. It is like running unbound with default settings sort of.Does NextDNS have ECS after 300k queries or does that fall under EDNS as well?
-
I'm facing the same issue.
I have run tests on 3 different computers, all the results showed Ashburn Cloudflare as DNS provider.
Just let you know, I always block outgoing 53 port .
This is really weird, isn't it? Why do I get the same Ashburn results as @myth0ne
-
The same thing happens to me when using NextDNS DoT on my router. Every once in a while it just hits cloudflare. But most of the time it doesn't. I am also using this on an ASUS router with Merlin firmware.
-
"status": "ok", "protocol": "DOT", "destIP": "45.90.28.247", "anycast": true, "server": "vultr-lax-1", "clientName": "unknown-dot"
-
I also got the Ashburn result. Perhaps this issue is on @dnsleaktest side.
client: apple-profile
-
Same problem. Android on 4g with private dns is giving me leaks. Tried different apps, all showing the same.
I have paid account.
test.nextdns.io returned
{ "status": "ok", "protocol": "DOT", "configuration": "fpef9e64ccdabf8a56", "client": "82.132.230.210", "destIP": "209.250.226.191", "anycast": false, "server": "vultr-lon-1", "clientName": "unknown-dot" }
-
Most of these leaks posted are showing different countries, Are most in this thread using a vpn?
-
For everybody in this thread reproducing the issue, could you please try with another DNS leak test service than dnsleaktest.com and report on if you can reproduce the issue or not?
The fact all leaks to different DNS providers are located in ashburn is highly suspicious and suggests a bug on dnsleaktest.com itself. The reason why it would only happen with us is a mystery though.
-
I don’t currently have NextDNS setup on my router anymore as it was causing issues for someone else’s device in the house. But, I will say browserleaks also showed odd behavior. It showed about a dozen google dns addresses as well as Cloudflare. I’ve never seen this happen with any other DNS. I don’t actually know what to make of these results as this shouldn’t be possible. Just wanted to report the odd results.
-
I came here to say that the same thing happens on https://browserleaks.com/dns (My IPv6 is disabled and I followed the entire tutorial step by step, but this problem happens even with everything ok.):
-
very odd, I do random ping & dnsleak tests but never had a problem using http://dnsleaktest.com/
-
I'm seeing similar “leaks“.
I use Safari on Big Sur (latest) with the NextDNS app.
I haven't seen this behavior on https://dnsleaktest.com, but sometimes on https://browserleaks.com/ip, and always on https://www.dns-oarc.net/oarc/services/dnsentropy.
Those other IPs from the DNS Oarc page are from Cloudflare somehow.
Test:
"status": "ok", "protocol": "DOH",
… … … "anycast": false, … … … … …
-
And for https://cmdns.dev.dns-oarc.net, I get a C result (while getting an A without NextDNS enabled).
Content aside
-
4
Likes
- 3 yrs agoLast active
- 119Replies
- 6272Views
-
17
Following