Asus Router DNS Issues — step-by-step fixes for DNS errors & name resolution
Updated: · Answered by Joe B. in 5 mins
Joe B.
Reviewed for technical accuracy
Specialities: Home networking, Wi-Fi routers, modems, Windows/macOS internet issues, DNS & IP configuration, ISP setup
Fix Asus router DNS issues — DNS server not responding, NXDOMAIN, ERR_NAME_NOT_RESOLVED, DoT/IPv6 DNS conflicts
Technician
Hi! We’ll get your Asus router DNS issues sorted so websites resolve instantly. Quick questions to target the fix: do you see errors like DNS_PROBE_FINISHED_NXDOMAIN, DNS server not responding, or ERR_NAME_NOT_RESOLVED on multiple devices? Which model (RT-AX86U, RT-AX88U, RT-AC68U, etc.) and firmware (Asuswrt or Asuswrt-Merlin) are you on? Lastly, in WAN > Internet Connection, is WAN DNS Setting set to “Get the DNS server automatically” or Manual with custom DNS?
Customer
It’s happening on everything — phones, laptops, the smart TV. Random sites won’t load and Chrome shows DNS_PROBE_FINISHED_NXDOMAIN. Router is an RT-AX86U on stock Asuswrt. In WAN settings I set manual DNS to 1.1.1.1 and 8.8.8.8 a while ago. We also turned on DNS over TLS (DoT). Since then, some apps time out.
Technician
Thanks — classic pattern. On ASUS, widespread DNS resolution failures usually trace to:
• Mis-matched DoT (DNS-over-TLS) settings or wrong TLS hostname for the resolver.
• Manual DNS that conflicts with IPv6 DNS or your ISP’s DNS filter / captive portal.
• DNS Director/AiProtection content filters intercepting DNS, especially with VPN/Ad-blockers.
• Stale device caches (DNS Client on Windows/macOS/iOS/Android) or corrupted DHCP leases.
We’ll test whether it’s a router-side DNS problem vs. device DNS, then harden your Asuswrt WAN DNS and client settings.
Customer
How do we test that quickly? I can browse to IP addresses like http://1.1.1.1 but domains fail after a few minutes. Rebooting the router helps for an hour then it breaks again.
Technician
Perfect symptom — transport works, name resolution doesn’t.
Step A — Quick isolation
1) On one laptop, set the adapter’s DNS to automatic via DHCP (not manual). Flush cache: Windows ipconfig /flushdns, macOS sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder.
2) On the same laptop, run nslookup example.com and note which DNS server answers (should be the ASUS router’s LAN IP).
3) In the ASUS UI go to WAN > Internet Connection. Temporarily set WAN DNS Setting to Get the DNS server automatically. Turn DNS Privacy Protocol (DoT)Off for now. Apply and test.
If lookups succeed with auto DNS and DoT disabled, we’ll re-enable DNS over TLS correctly with a supported provider hostname and make sure IPv6 DNS isn’t fighting IPv4.
Customer
After switching to “Get DNS automatically” and turning off DoT, sites load immediately. nslookup shows the router’s IP answering and no NXDOMAIN. But I’d like to use secure DNS again if possible.
Technician
Great — that confirms the router DNS path was the culprit. Let’s bring back encrypted DNS safely.
Step B — Correct DoT on ASUS
• In WAN > Internet Connection, set WAN DNS Setting to Manual and toggle DNS Privacy Protocol to Strict (DoT).
• Enter resolver TLS hostnames exactly (e.g., Cloudflare: cloudflare-dns.com; Quad9: dns.quad9.net) and keep their IP fields blank so the router resolves them correctly.
• In IPv6, either set Get IPv6 DNS automatically or mirror the same provider (Quad9/Cloudflare) to avoid IPv6 DNS leaks that trigger ERR_NAME_NOT_RESOLVED on some devices.
• If you use DNS Director or AiProtection Adult Content Filtering, ensure profiles aren’t redirecting queries to another resolver — that double-NATs DNS and causes intermittent DNS server not responding on clients.
Apply, wait 60 seconds, then run nslookup again. We want stable answers with low latency.
Customer
After setting DoT with the provider hostname, lookups work again. But one gaming PC still throws DNS_PROBE_FINISHED_NXDOMAIN after waking from sleep. The others are fine.
Technician
That’s a local cache/lease hiccup.
Step C — Windows client fix for persistent NXDOMAIN
1) Ensure the adapter DNS is set to Obtain automatically (no leftover manual DNS).
2) In admin Command Prompt: ipconfig /release → ipconfig /renew → ipconfig /flushdns.
3) In Power Options, disable Fast Startup (it can preserve stale DNS states).
4) If you run a VPN/Ad-blocker (Wintun/WinDivert/NextDNS/AdGuard), temporarily disable to ensure they aren’t overriding the router with their own DoH resolver.
5) On the ASUS router, under LAN > DHCP Server, make sure the lease time isn’t extremely long (e.g., set 86400 seconds) and that the PC gets the correct gateway/DNS (router LAN IP).
Customer
Did that sequence and the PC is working now. If this returns, is there a way to force the ASUS to hand out the same DNS to all clients and bypass device-side DoH?
Technician
Yes — keep things consistent from the router down.
• In LAN > DHCP Server, set DNS Server 1 to the router’s LAN IP so clients query the ASUS first (it will relay to your DoT provider).
• If your firmware includes DNS Director, create a rule pointing all devices to “Router” as the resolver. Avoid per-device profiles unless needed.
• Keep IPv6 on either full auto or fully manual — mixing can create dual-stack mismatches.
• Turn on Router time sync (NTP) under Administration > System; incorrect time breaks TLS and causes DoT failures.
• Update to the latest stable Asuswrt (or Asuswrt-Merlin if you use it) — several builds fixed stubby/dnsmasq quirks that looked like random DNS server not responding.
Customer
After updates and standardizing DHCP, everything’s solid. Any tips to prevent DNS errors from coming back monthly?
Technician
Absolutely — a few best practices for Asus router DNS issues:
• Keep just one encrypted DNS method (DoT or device-side DoH), not both.
• Avoid stacking AdGuard/NextDNS on devices if the router already filters DNS — choose one enforcement point.
• If you enable Dual WAN or failover, copy the same DNS/DoT settings to the secondary to avoid resolver flips.
• Periodically clear the router’s System Log and reboot after firmware upgrades to refresh dnsmasq and stubby.
• Save an export of your config once stable. If anything goes sideways, restore and you’re back in minutes.
Customer
Got it. With DoT properly set and the DHCP changes, the family hasn’t seen a single NXDOMAIN or ERR_NAME_NOT_RESOLVED today. Thanks!
Technician
You’re welcome! Summary: For Asus router DNS issues, test with auto DNS, then configure WAN DNS and DNS over TLS with correct provider hostnames, align IPv6 DNS, standardize DHCP so clients use the router, and clear device caches. If you hit obscure errors like DNS_PROBE_STARTED or DoT timeouts, open a chat — we’ll trace it live and lock it down.
Customer
Perfect. Everything’s loading fast again. Appreciate the detailed walkthrough!
Technician
Any time! If a friend complains that their ASUS router says DNS server not responding or shows DNS_PROBE_FINISHED_NXDOMAIN, share this checklist — or start a chat with an expert and we’ll fix it together.
Quick answer: the accepted fix
Accepted fix for Asus router DNS issues: switch WAN DNS Setting to automatic and disable DNS over TLS to test; if stable, re-enable DoT with the correct resolver TLS hostname, align IPv6 DNS with IPv4, ensure DHCP hands out the router as DNS, and clear device caches to stop DNS_PROBE_FINISHED_NXDOMAIN/ERR_NAME_NOT_RESOLVED.
Why ASUS routers have DNS errors (DoT, IPv6, DHCP, filters)
Most ASUS DNS problems stem from incorrect DNS over TLS hostnames, conflicting IPv6 DNS, mixed device-side DoH with router-side DoT, or aggressive DNS Director/AiProtection filtering. Firmware updates that refresh dnsmasq and stubby often improve stability and reduce DNS server not responding messages.
Break the path down — device → DHCP/DNS on router → upstream resolver → internet. If direct IPs work but domains fail, it’s almost always configuration on the router or the device’s DNS cache rather than your ISP connection.
How to tell if it’s router DNS or device DNS
Use nslookup/dig to see who answers. If the ASUS LAN IP responds but times out, switch WAN DNS to automatic and disable DoT to confirm. If that fixes it, re-enable DoT with proper provider hostnames. If only one PC fails, clean its DNS cache, renew its DHCP lease, and remove manual DNS or interfering VPN/ad-block DoH.
Asus router DNS issues — quick troubleshooting tips
Standardize DNS at the router, then re-enable encryption cleanly.
Fast path: set WAN DNS Setting to automatic → turn DoT off to test → verify lookups → turn DoT back on with correct TLS hostname → align IPv6 DNS → ensure LAN DHCP gives out the router as DNS → flush device caches. Keep firmware current and avoid stacking device DoH with router DoT.
Disclaimer: This information is AI-generated and intended for general guidance only. For advice specific to your ASUS model and ISP, please consult a verified expert on Whizz-Tech before making decisions.
Getting Started Is Easy
Ask for help, 24/7
Members enjoy round-the-clock access to 12,000+ verified Experts for ASUS DNS issues, DNS over TLS setup, IPv6 DNS, and more.
Expert will respond in minutes
We match you with a networking specialist who knows Asuswrt, DNS Director, DHCP/DNS, and secure DNS for all ASUS models.
Save time & money
Stop chasing DNS_PROBE_FINISHED_NXDOMAIN or DNS server not responding. Get a clear step-by-step DNS fix in chat and get back online quickly.
FAQ
Why does my ASUS router show “DNS server not responding”?
Common causes include incorrect DNS over TLS hostname, mixed IPv4/IPv6 DNS settings, device-side DoH overriding router DNS, or filtering via DNS Director/AiProtection. Switch to automatic WAN DNS to test, then re-enable DoT with the correct provider hostname.
How do I fix DNS_PROBE_FINISHED_NXDOMAIN on all devices?
Standardize DNS at the router: set WAN DNS to auto, confirm lookups, then configure DoT with the proper TLS hostname and align IPv6 DNS. In LAN > DHCP Server, hand out the router’s LAN IP as DNS. Finally, flush caches on devices and renew DHCP leases.
Can I use both DoT on the router and DoH on devices?
You can, but it often causes inconsistent resolution and policy conflicts. Choose one encryption layer — preferably router-level DoT so parental controls and DNS Director policies remain effective across the network.
When should I reset ASUS DNS settings or the router?
If DNS fails even with automatic WAN DNS and no filters/VPNs, back up your config and try a factory reset. Then re-apply essential settings only: ISP login, Wi-Fi, and DNS. Test before turning on extras like AiProtection or VPN Fusion.