
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.
-
What do you get for https://test.nextdns.io?
-
If you configured only the v4 DNS and you didn't configured or disabled v6 you will have leaks.
If possible use DoH or DoT as explained in the links I gave you but probably didn't bother reading.
If you can install the CLI, if not other app/client or some script that can be configured with DoH or DoT. Or disable V6.
https://github.com/nextdns/nextdns/wiki
*You can try the servers direct ip's, see if they work... I say they won't and I think you should stick with the ones from your profile.
-
losnad said:
If you configured only the v4 DNS and you didn't configured or disabled v6 you will have leaks.
If possible use DoH or DoT as explained in the links I gave you but probably didn't bother reading.I did read the article. I can only use v4 or v6 links. I've disabled v6 on my router and pihole config
When I sign into my dashboard I even get the following -'IPv6
Your network does not support IPv6'
-
It's normal to not know, no one was born a master.
To don't listen, to not read to learn, this is not normal.
If you have leaks in DNS where NextDNS and other DNS providers appear on the same time it's probably a problem with v6 which is not configured or can't be configured.
If NextDNS does not appear at all, it is most likely because you did not configured DDNS and your IP is dynamic. I mean is not rocket science. Your IP change, you no longer use NextDNS.
Set the default NextDNS 45.90.28.0 and 45.90.30.0 and it will act just like any other public DNS like Cloudflare or Google. But you will lose all your settings from the account. If you use the IP from your account you need to either have a fixed IP or update it when is changing, manually or to set up a DDNS.
It is all explained in your account, here on Knowledge Base. But it is easier to just complain when is clearly nothing wrong with the service but just human error.
Now, just ignore, again, what I explained and keep having the same problem.
-
losnad said:
If you have leaks in DNS where NextDNS and other DNS providers appear on the same time it's probably a problem with v6 which is not configured or can't be configured.
If NextDNS does not appear at all, it is most likely because you did not configured DDNS and your IP is dynamic. I mean is not rocket science. Your IP change, you no longer use NextDNS.I am trying to help us out here to say I am not reading or listening helps nobody and comes off as stubborn.
It isn't just me as I can see it appearing on other threads here as well.
To reiterate some of the suggestions you have made. I have IPv6 straight up disabled from my router. I don't have it set up at all and only utilise ipv4. In regards to a dynamic IP that is also incorrect as I have a static ip given to me by my ISP.So rather than telling me I am not listening and ignoring what is said, if we as fellow people in the tech field where does it now take us with the next troubleshooting steps moving forward now you know this information which might I add I already mentioned in the thread previously?
-
A quick thing and I'm done, one thing is for sure, NextDNS does not redirect you or the others who have problems to Cloudflare or any other DNS providers.
In this situation, there is nothing wrong with NextDNS service. If you don't know or want to learn how to use it, ask someone to check your setup.
-
Yeah, instead of reading Knowledge Base https://help.nextdns.io/category/knowledge-base
you read on reddit.
https://help.nextdns.io/t/p8hmvaw/what-happens-after-300k-queries
-
Did you link your static public IP from your ISP? If not, you'll need to do that if ipv4 is your only option
If so, do you have more than one static DNS entry setup on your router's side? If so, pihole recommends only having one entry (setup to your pihole's IP)
https://discourse.pi-hole.net/t/how-do-i-configure-my-devices-to-use-pi-hole-as-their-dns-server/245
Your NextDNS ipv4 DNS servers (from your dashboard) will need to be entered as the ONLY custom ipv4 upstream DNS entries via pihole
Or You can use Pihole as the DHCP server instead of the router
-
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?
-
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" }
-
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/