No reply from NextDns.IO DNS Servers on Windows with YogaDNS
The problem started this morning (approx. 9:10 CET). We are not able to lookup DNS using the assigned DNS servers of NextDNS. If we revert to the DNS Servers of our ISP or Google DNS (220.127.116.11) everything work fine.
Any input on how to investigate an solve? Thank you!
Same here. Every day there is a 10+ minute window when it doesn't work.
This service is not worth paying for :(
We've also been seeing this, starting this morning or possibly even yesterday evening in the central United States (Texas). Timeouts on DNS over HTTPS queries. This is affecting several—but not all—users at different locations in the area. For other users it's working fine, so I'm guessing the problem is with a few particular servers in NextDNS's infrastructure. Affected users have switched to another DNS resolver as a temporary workaround.
Please provide information about your setup.
I have this issue too, on my Windows 10 laptop, accessing NextDNS via YogaDNS with the dedicated NextDNS server protocol option.
- Responses are intermittent. Some are successful while most timeout. There is no pattern to which domains are and are not getting responses: some domains are both successfully resolved and timeout at different times.
- Deleting the NextDNS rule and reverting to the default causes all requests to be successful.
- Adding a new server using the DNS over TLS protocol and NextDNS as the target causes all requests to be successful, as expected.
- My phone using DNS over TLS in Android's private DNS setting also works as expected.
I did get this message in the log:
> DnsCrypt log: Get https://dns.nextdns.io/[ID redacted]/[Device Name]?dns=[Long ID redacted]: x509: certificate signed by unknown authority
YogaDNS 1.19 / Driver Version 117 as displayed in the log
Hi all -- I wanted to jump on here and report the same issue. Earlier this morning (~7:30 pacific) neither of my Windows PCs using the most recent YogaDNS client could resolve DNS, but my iOS device was fine. I didn't have time to troubleshoot since I had a meeting to get to, but quitting YogaDNS "fixed" it. IIRC I came across a reddit post about this as well where someone reinstalled YogaDNS and it started working again. Maybe related to recent cert updates announced on 5/31?
I'll also try to diag the problems next time it occurs in Switzerland.
I believe I’ve run into this again this morning. Is this a known/ongoing issue, and/or anything other than what’s outlined above that I could do to permanently resolve it?
I had the same problem with YogaDNS, but it seems to working again for me. I am experiencing some high ping times from my fortigate. It happened exactly when YogaDNS starting getting timeouts.
- 2 yrs agoLast active