NextDNS issues with DoT on ASUS Merlin
Been having some issues for a while now when using the DoT functions natively supported in ASUS Merlin. Pages time out and often will sit with an "error not resolved" message for roughly 4-5 seconds before the page will refresh and load content.
(This happens with or without DNS Filter active; Model AX-88U)
I have done a complete reset of the router, and used the NextDNS CLI (which doesn't have errors, but resolves slower) but for whatever reason the NextDNS DoT implementation doesn't seem to like the ASUS Merlin firmware anymore, or there's a CDN issue with DoT for the Atlanta region.
I have since disabled any options within the Performance tab of the website, and still am having issues. To the point that many of the diagnostic services for NextDNS itself will not work or report well. Options on the router are minimal outside of factory defaults, with IPv6 and DoT setup being the only noteable changes.
My ISP is AT&T U-verse/Fiber.
I preferred the DoT implementation as hostnames from the CLI can flood the logs with various (blank) names, and the DoT doesn't have to be regularly updated.
Good morning/afternoon everyone.
Sorry to bump this topic, but I think I may have figured out what's causing the issue (fingers crossed) regarding the ASUSMerlin DoT implementation, and NextDNS...
I noticed after using the DoT method, that pages were failing to resolve with "ERR_NAME_NOT_RESOLVED" as the Chromium error message.
What I've discovered (SO FAR) is there's an issue with handshake/authentication with NextDNS services for some reason when this option is set to STRICT.
I don't know if this is due to using a device name for the DoT resolution, "AX-88U-XXXXXX.dns.nextdns.io" or something else.
I'm unsure if this is an authentication factor on NextDNS's behalf, or some handshake requirement of ASUSMerlin... but I can confirm (with optimistic hesitation) that setting to OPPORTUNISTIC has resolved my DoT issues so far.
I will bump/update if the problem continues after this adjustment.
After some time of testing NextDNS I can confirm that Strict or Opportunistic, or dns1 vs dns2, the issues will still arise. It SEEMS to be related to something with IPV6, which had previously not given me any issues. I am on ATT U-verse which does support native IPV6 dual-stack, and from what I can tell, anytime I start having the issues with connectivity, then the NextDNS status page indicates that my network does not have IPV6 capability.
It's possible this is ISP related, but that may be difficult to confirm... moving to another DNS resolver (Quad9/Cloudflare) works well, so I don't know if it's a service pipeline issue from ATT to NextDNS in Atlanta, or if there's something else going on with the IPV6 service for NextDNS in Atlanta.
Thank you for all your time and help, for now, I have disabled IPV6 and will continue testing.
Hate to bump an old thread but I am seeing this issue as well. Exact same behavior as @BS except I am using stock asus firmware which now supports DoT, and I am IPv4 only. I have used Cloudflare DoT successfully for a while. About 12 hours after setting up nextdns I am unable to resolve any domains on my network. @NextDNS Can you guys take another look into this please? @BS do you have any updates? Thanks in advance!
I finally had to revert to using non-NextDNS resolves about a week ago. The family kept complaining about unresolved DNS issues on Merlin manual setup with DOT. I've been doing this a while and had issues at first...but something's been escalating. I was rebooting the router about every 48 hours just to keep the family happy (DNS would just stop working)... No, I do not use the "agent" and have been using manual setups for 2 years.
I've given up using NextDNS DoT with Merlin. I'm using DoH without issue.
Just an update: I've not had any complaints in the past week to the "home IT department" about DNS not working and sites not resolving since I removed the NextDNS configuration from my ASUS Merlin setup (386.3_2) - which I've been running for ~ 9+ months. (I've not upgraded to the latest 386.4 b/c of known issues...) I've also not had to reboot the router to recover DNS stability not once after I reconfigured the main router to a DOT/Quad9 configuration. That delivered stability but sadly none of the NextDNS benefits. I'm monitoring this thread and others for further progress by the NextDNS team on the issues being reported here. Stay safe, stay warm. Thanks! Peace.
Any updates to this issue yet @NextDNS
- Status Fixed
- 1 yr agoLast active