Short-term outages with DoT
I have set up the "DNS-over-TLS/QUIC" address in my Android smartphone as "private DNS" and also in the router for the home network. Basically, the service works very well, but several times a day I have short-term outages of up to 30 seconds on all end devices, both at home and mobile, during which no address can be resolved.
The problem apparently only occurs with the natively supported protocol DoT. If I only enter the unencrypted IPv6 DNS server in the router, I cannot determine any comparable failures so far.
https://nextdns.io/diag/6bddc480-68e8-11ec-987f-9119e8b922f7
-
The problem also exists via smartphone in the mobile network - so I can rule out the router as the sole source of the error.
As a temporary measure, I now use the DoH entry on the systems that natively support it (Chrome, Windows 11). This way, uninterrupted web browsing is at least possible. However, I do not consider this setup ideal. I do not want to install additional apps and they are not available everywhere (e.g. router).
-
I've got the same issue, router-based DNS-over-TLS. ping.nextdns shows as if anycast servers have appeared to be dead.
-
I have a Netgate pfSense router experiencing the same issues with DoT configs except my outages are for longer periods of times, sometimes up to 10 minutes.
Not only is my router unable to resolve addresses, the two iphones I have in the house directed to NextDNS DoT DNS servers were not resolving.
After complaints from family members about TVs, laptops, etc not working i had to divert to the plain-text configs.
Also, this isn’t a new issue. It appears often and it’s quite annoying.
-
JCVR
i cannot confirm that but i will. i’ve just been lazy and put all my eggs in the NextDNS basket trusting it would work. Perhaps i’ll see the same issue with other providers, i don’t know but i’ll switch to AdGuard to compare stability.
-
-
That last time this happened it was an issue with Stubby not gracefully handling slow handshakes with NextDNS, which was supposed to be fixed, but I do know there was an issue filed on the Stubby GitHub regarding this as well.
TLS Connection Failures - Stubby - Bug Reports - NextDNS Help Center -
I have now tested personal AdGuard DNS beta intensively for two days. No timeouts via DoT so far, neither natively via my Android smartphone nor via my router. Also, the name resolution seems a little bit faster to me, but may just be imagination.
The range of functions of AdGuard DNS is still quite limited. The interface is also not as innovative and clear as NextDNS. Yet!
So @NextDNS, use your advantage over the upcoming competition and finally fix the problems with DoT! :-) I would like to stay here as paying customer.
-
Koboldchen can you please try with anycast.dns.nextdns.io and tell us if you can reproduce the issue?
-
NextDNS Yes, happened right now again on my smartphone at 8:37:04 a.m. CET accessing to golem.de from IP 109.250.66.1 / 2001:9e8:2706:3800:b9f2:5812:d8b4:68d5.
-
Koboldchen we will deploy a tentative fix today, I’ll keep you posted.
-
JCVR there is no known issue with DoH. This is a potential fix for DoT although we couldn’t reproduce the issue so we need field testing to confirm.
-
JCVR it's fully deployed, please tell us if you see improvement or not.
-
NextDNS Thank you very much! I'll check it out and get back to you.
-
Everything is the same as before
I just could not open the sites, after 3 seconds it worked. Then the same with other sites.
NextDNS
-
NextDNS Not the OP, but still having timeout issues with using DoT on ASUS-Merlin.
-
Thanks for testing. Could please now test with the following hostnames *one at a time* and report if one or the other is fixing the issue:
-
NextDNS Can also confirm that the fix yesterday didn't solve the problem. Will try the anycast addresses now.
-
NextDNS Any new knowledge here? As JCVR has already confirmed, there are still infrequently resolving issues with the alternative addresses.
-
JCVR we just pushed another tentative fix, please report if it does change anything.
-
NextDNS Sorry, just had the next dropout on my phone again (private DNS in Android).
-
JCVR is your script sending queries at a fast pace?
-
JCVR please send me your IP over DM and the output of https://test.nextdns.io so we can investigate.
-
JCVR we think found the issue. It will be deployed in the next few days. Stay tuned.
-
NextDNS I can confirm that the problem seems to be fixed for me as well. Thank you very much!
-
NextDNS Can you please confirm this has been resolved? "Stay tuned" but no official announcement.
-
BS the issue has been fixed. We communicated on the other thread: https://help.nextdns.io/t/x2hfpfk/nextdns-down
-
-
I need some help please
https://help.nextdns.io/t/q6hjt2p/nextdns-not-working-through-wireguard-vpn-server
-
Using AdGuardHome and forwarding upstream to the dot://url or doh://url and then checking the hit counter in NextDNS Analytics.. I found that doh was (almost) 3x used than dot.
Unbound and Core can use dot as a recursive forward.. and dnscrypt-proxy can only do doh
I've used clash (proxy) which can support dot doh directly.. but I have way to prove how it's goes from one to the other.. I was also trying to name the nextdns-cli to see how that appears in the logs.. but it seems to just come from the ip address of the wan connection it is coming from..
I can't seem to name that endpoint like you can with dot://dot-custom-name-123abc.dns.nextdns.io or doh://dns.nextdns.io/123abc/doh-custom-name
I'm not sure if AdGuardHome had problems with dot and that is why the count was uneven..
My 0.02
-
Same issue here with DNS over TLS.
I have an Asus router with NextDNS TLS address input manually. Either it stops working on a reboot or the connection just drops randomly. I also ditched the cli client as that wouldn't reconnect on a reboot
-
I just started encountering issues today with DoH failing only for v4, v6 is still resolving fine and I see it in my NextDNS logs, yet I am getting no return on v4 addresses, I needed to fallback to Cloudflare for v4 but have continued testing with the NextDNS DoH v4 issues.
Were any changes made today? Or could this be my ISP doing some form of DPI that is messing with my encrypted DNS?
