DNS Connection and Filtering was gone for a whole day
Today I went on to use my phone normally. (Instagram, Tiktok, Netflix, you know) But I have one app that contains ads. A football app. When I'm connected with NextDNS I dont see ads but I did. So thats why I went to my dashboard and checked it out.
And it said, that my device isn't connected to NextDNS. Im using the Private Dns feature from Android. And normally it would say something like "No internet connection, cant connect to DNS provider". But this time, it didnt. So there was no error on the client side, but on NextDNS. (Probably)
And when i looked into my Protocols, I saw that NextDNS didnt got any DNS requests from me, the whole day. And even more bizzarr was that the the order of the dns protocols was/is mixed up.
And the newest protocols are from 20 mins ago.
Am I the only one having this issue?
Is there maybe a way to get notified when Im not connected to NextDNS? Or at least something? I dont want to check my dashboard all the time to know, if im connected or not...
13 replies
-
Or even right now: The website says: "This device uses NextDNS without configuration.
Make sure the DNS-over-TLS endpoint shown below is used."
My phone didnt gave me a notification saying, that it couldn't connect to NextDNS. Ad-blocking doesn't work right now.
So what is the issue here?
-
Ok i got the issue. So when using DNS over TLS, i added my device's name to the url. (For example: "Iphone11-xxxxx.dns.nextdns.io") when using this, nextdns gives me the error above (that im connected without a configuration)
But without the device name in the DoT url, it works normally.
Please fix this issue
-
S F That sounds like an android issue with the DoT string. Was there an update to your device recently that could have caused the change in behaviour?
-
R P MI had updates but i dont know if they affected anything. Is there a way for me to automatically get a notification when I'm connected "without any configuration" ?
Because It is like this: when I change it on and off again, nothing changes. But when I add a device name (e.g: S21-myurl.nextdns.io, instead of myurl.nextdns.io) then it works again. And after sometime I have to remove that device name again from the url so that It works again. Very weird.
-
@r_p_m is there maybe any way of automatically checking if im coneccted correctly and not with "connected without configuration"? Maybe with the new API feature? Thanks
-
I don’t think there’s anything on android to automatically check the connection. Maybe try the NextDNS app as an alternative? Or if you want to set your device name manually try any other secure dns app and put in the string yourself.
-
Given your description of the issues, it sounds like the problem is with the way "MI" is handling DoT. You want to find other people using the same phone and OS version to compare.
The next time DoH fails and you start to get ads. Check what DNS provider your phone is actually using by going here https://www.dnsleaktest.com/ Run the test. The results will show your what DNS IPs your phone is actually querying to.
Most likely your phone is defaulting to google's IPs.
NextDNS does provide a way to test if your device is using nextdns https://test.nextdns.io/ but I don't know if when not using nextdns the test would yield what DNS ips the device is actually using. Test it out.
-
hi, so it happend again and i ran a few DNS leak tests as you wished.
The results were the same on every website. Im very certain that my device is not using Google's DNS. I tried these tests with ("dns.google") and the websited showed me a whole diffrent result.
And when not using any TLS DNS. (So if I use the dns of my provider) i also get diffrent results, with the name of my Provider.
So i dont know
. I personally think its an issue on the part of NextDNS. Please help me with that -
At least you are right about something, "you don't know".
I personally think it's an issue with you not knowing what are you doing. Which is normal for most of us. The difference is that most of the people read the instructions, read the Knowledge Base, read the comments section, read on Wikipedia or search the internet to learn before making allegations and wasting people time.
If on my.nextdns.io - Setup you get «All good!
This device is using NextDNS with this profile.» and/or on test.nextdns.io says «Status: OK» it's working normally.
NextDNS use many networks like Misaka, Anexia, Zepto, Edis etc.
Most likely you are using anycast and if you read you will learn how to set up and use ultralow.
It's funny that you masked the IP of the DNS...
-
so. What do you recommend next? If it is an OS issue, there is nothing I can do. Is there a way of hourly checking my dns connection without opening the Dashboard?
-
The idea of the tests were to try and see if when "it fails" the devices were some how switching to its own DNS.
The DNS Leak Test: to run the extensive test to see if your phone some how was querying more DNS providers than the one you have set (nextdns). The test.nextdns.io test is to make sure you are using nextdns.
Because I find odd that a mere edit of the DoT DNS query domain results on ad-blocking working again, is what made me think that perhaps something is wrong with the way MI handles private DNS but in reality there are many factors that could be the issue. For example, it could be your ISP blocking DoT and rerouting those queries to their DNS.
-
-
Not everything is about the OS. People were using NextDNS or other encrypted DNS providers before the OS's included ways to set it up.
I don't know what is going on with your device, sometimes I scratch my head with my own problems, but one thing is sure, the chances of being something wrong with NextDNS are almost zero. I using it since beta and the DNS servers always work. There were other kind of rare issues.
Some implementations ask for the the complete link for encrypted DNS, for example:
quic://DeviceID-ProfileID.dns.nextdns.io tls://DeviceID-ProfileID.dns.nextdns.io https://(doh3.)dns.nextdns.io/ProfileID/DeviceID
Some problems can be with the devices, some don't support encrypted DNS, if you have the issue with an android phone you can try the NextDNS app, it uses DoH. This will prevent you from using most VPN, if you use one. Some devices provided by the ISP don't allow you to change the DNS, or worse, it looks like you can but it ignoring it. You can't install the nextdns.io/CLI on all devices... For this situation you can buy /use your own router...
There are other apps, Nebulo, Intra, etc. I personally use AdGuard app in which I can use DoH, DoT, DoQ. You can look at the link from my profile or read my previous posts here. You can use the search function to look for posts about Nebulo etc.
In some cases the problem is with the internet provider which is blocking the DoT. Using another protocol might work.
Content aside
- 1 yr agoLast active
- 13Replies
- 276Views
-
3
Following