NextDNS unavailalbe for small time-frames daily
Hi,
I am a rather new (paid) customer of NextDNS and have started facing some issues since I updated my router to use NextDNS.
I have a FritzBox 7530, configured with FTTH connectivity (1Gbps/300Mbps) which had never failed to resolve DNS when I was using either Cloudflare DNS (Regular DNS + DoT), Quad9 (Regular DNS + DoT) or Google DNS (Regular DNS + DoT).
Since I switched to NextDNS about two weeks ago, and I have configured the router in the same way, inserted the 2 IPs from the Installation Page, and configured DoT, after having associated my public IP and its alias (No-IP).
As a matter of facts, daily, I am seeing some DNS resolution errors for any device connected to the FritzBox. I can't resolve any site during this time, whether I type google.com, bing.com, or anything else for the matter.
I have tried to leave the blocklists on, change the blocklist configuration, remove them all, to remove all security features, disable logging (which was previously enabled) - nothing made a difference and the service kept being unavailable for approx. 5 minutes, continuatively, per day - sometimes it have happened twice in a day.
When the unavailability was faced, my public IP did not change, I have verified that, so I can exclude it was due to the associated IP having changed.
If it makes any difference, my network submits approximately 40,000 queries per day.
It's rather frustrating to have a paid service perform worse than a free service, so I would appreciate some help in getting this issue resolved.
Thank you very much.
7 replies
-
Does the Fritzbox provide logs of what happens during those interruptions?
Is there a pattern in terms of timing (always happening at the same time of day)?
-
Hi,
Sadly not, the Fritzbox does not provide any log, and no events are recorded.
As of timing, it happened around 09:00 GMT this morning, yesterday it happened around 16:30 GMT. On the Fritz there are no scheduled task, and if I try to ping any address (i.e. 8.8.8.8 or any other IP), the ping is successful. Likewise, if I try to access a test website hosted on Azure, for which I have a dedicated public IP, I can access it via its IP but I can't access it via its FQDN as the name resolution fails.
Generally it seems to me that these disservices mostly happen mid-morning or early evening.
If memory serves, the errors I was getting in Chrome and Edge were like ERR_NAME_NOT_RESOLVED, ERR_DNS_FAIL, and others, which do not come to mind. At the same time, Microsoft Outlook showed offline, meaning it could not resolve outlook.office365.com and Teams was offline too.
Thank you.
-
I can absolutely exclude it’s a router issue.
The problem reproduced over multiple firmware version, over a factory reset and reconfiguration, and I was able to reproduce with another Fritz 7590 I could put my hands on.Thanks.
-
I have a similar problem with my new fritz box 6690 cable in germany / vodafone cable. switched to adguard with DoT on my local network with no problems. I hope nextdns will get this issue solved, since I subscribed it and like the concept.
-
I have just ordered a Unifi Dream Machine Special Edition.
I will try NextDNS on this new enterprise-grade hardware and check if it works there.Since I switched to Cloudflare DoT, on the same FritzBox, a week ago, I haven’t had a single issue or DNS resolution issue. This confirms once more that the issue is not caused by the device but rather from the service.
@NextDNS, would you have any suggestion on how to troubleshoot this further?
-
Hello,
I have exactly the same issue. This happens a few times a day. The internet connectivity is fine, just no connection to Nextdns. Querying Nextdns servers times out, while querying 1.1.1.1 is no problem at all.
I know it's an old thread, so maybe you have found a solution in the meantime?
Thanks,
Jonas
Content aside
- 10 mths agoLast active
- 7Replies
- 200Views
-
5
Following