What's going on

When your device shows connected Wi-Fi but displays errors like "DNS_PROBE_FINISHED_NXDOMAIN" or "Server IP Address Could Not Be Found," your internet pipeline isn't completely dead—it has lost its phonebook. Domain Name System (DNS) is responsible for converting human-readable web addresses (like example.com) into numerical IP addresses (192.0.2.1).

When a router's internal DNS service stalls, or when your Internet Service Provider's (ISP) upstream DNS servers go down, your computer can still send raw data packets across the wire, but it cannot translate website names into destinations. This is why active VoIP calls or direct IP connections might continue working while new web browsing comes to a complete halt.

Explore broader connectivity issues on our /problems/routers guide or browse our /reviews for hardware performance evaluations.

Symptoms people notice

• Web browsers crash on lookup: Sites fail with explicit errors like ERR_NAME_NOT_RESOLVED or DNS_PROBE_FINISHED_BAD_CONFIG.
• Selective app functionality: Background messaging apps or established gaming streams stay online, but clicking any new hyperlink fails.
• Status bar delay: Browsers linger on "Resolving host..." for 15–30 seconds before timing out.
• Mobile device workaround: Disabling Wi-Fi on your phone instantly allows web pages to load via cellular data.
• Network-wide impact: Every phone, laptop, and smart TV connected to the same router experiences identical address lookup failures.

Likely causes

1. ISP Domain Resolver Outage: The primary DNS servers assigned automatically by your Internet provider are down or experiencing high packet loss.
2. Stuck Router Daemon: The lightweight local DNS relay service running on your router (dnsmasq or similar) has crashed in system memory.
3. Misconfigured Custom DNS: Static DNS IP addresses previously typed into the router settings are offline, outdated, or contain a typo.
4. Security & Content Filtering: Built-in router protection services, malicious site blockers, or parental control software are erroneously dropping domain queries.
5. Stale DHCP Lease Info: Connected devices held onto obsolete DNS server IPs assigned before a network change or router restart.

Quick checks first

Before digging into deep router administration menus, try these quick diagnostic steps:

• Ping an IP directly: Open Command Prompt or Terminal and type ping 8.8.8.8. If the ping receives replies, your physical line and gateway are healthy—DNS is definitely the point of failure.
• Try a secondary device: Check if the issue happens on both a mobile phone and a desktop computer. If it only occurs on one device, the problem is localized to that operating system's network stack.
• Bypass the router temporary: Connect your computer directly to your modem with an Ethernet cable. If websites load, the issue resides entirely within your router's operating system or configuration.

When it's a real hardware fault

Most DNS failures are software-based state corruptions. However, severe internal hardware faults can cause recurring resolution drops:

• Flash Storage Wear / System Corruption: Aging home routers with degraded flash memory can corrupt system configuration files during power fluctuations, causing system daemons to fail on boot.
• Thermal Throttling & Power Supply Failure: A failing power adapter or an overheated System-on-Chip (SoC) can drop CPU clock speeds, leading to buffer overruns inside the router's DNS query processing queue.

If your router regularly drops DNS services every few hours even after a full system reset, the internal board or flash storage is deteriorating. Learn more about device lifespans in our /devices hardware section.

Soft resets vs board/panel work

Resolving DNS failure almost never requires hardware disassembly or board repair. Over 95% of DNS errors can be solved through soft configuration changes:

• Soft Fixes: Rebooting the gateway, clearing local DNS caches, assigning public resolvers (Cloudflare 1.1.1.1 or Google 8.8.8.8), or performing a factory software reset via the admin dashboard.
• Hardware Reality: Home consumer routers do not have user-serviceable logic boards or DNS modules. If a router consistently corrupts its operating system memory despite clean firmware re-flashes, replacing the physical unit is far more reliable and cost-effective than attempting circuit-level repair.

Next steps

1. Apply Public DNS: Log into your router console and switch from ISP DNS to 1.1.1.1 and 8.8.8.8.
2. Clear Client Caches: Flush the DNS cache on your PCs, Macs, and mobile devices.
3. Update Router Firmware: Install the latest software update from your manufacturer's support portal to patch potential memory leaks in the DNS daemon.
4. Perform Factory Reset: If domain resolution continues to stall, press and hold the recessed reset button on the back of the router for 10–15 seconds to return all routing tables to stock settings.