How to Fix "DNS Server Not Responding": A Complete Troubleshooting Guide

Last Updated: October 2026

What Does "DNS Server Not Responding" Mean?

Every time you type a URL like example.com into your browser, your operating system sends a query to a DNS (Domain Name System) server asking it to translate that human-readable name into the numerical IP address the internet actually uses for routing. The DNS server is essentially the internet's phonebook — without it, your browser has no idea where to send the request.

When you see the "DNS Server Not Responding" error, it means your device sent a DNS query but received no answer within the timeout period. The browser cannot resolve the domain name, so it cannot load the page. Critically, this does not necessarily mean your internet connection is down. You might still be able to reach IP addresses directly (for example, pinging 1.1.1.1), but anything that requires name resolution — which is virtually every website — will fail.

This error appears differently depending on your browser and operating system. Chrome may show DNS_PROBE_FINISHED_NO_INTERNET or ERR_NAME_NOT_RESOLVED. Firefox displays "Hmm. We're having trouble finding that site." Windows network diagnostics will explicitly report "DNS Server Not Responding." Regardless of the wording, the root cause is the same: the DNS lookup failed.

For a deeper understanding of how DNS works under the hood, see our What Is DNS? guide.

Common Causes of the "DNS Server Not Responding" Error

Before diving into fixes, it helps to understand what typically triggers this error. Knowing the cause narrows down which solution will work for you.

1. ISP DNS Server Outage

Your Internet Service Provider runs DNS servers that your router is usually configured to use by default. These servers handle millions of queries and occasionally go down for maintenance, experience overload during peak hours, or suffer outages. When the ISP's DNS is unreachable, every device on your network that relies on it will fail to resolve domains. This is the single most common cause of widespread "DNS not responding" issues and is also the easiest to fix — just switch to a different DNS server.

2. Router or Modem Issues

Your router acts as an intermediary between your devices and the DNS server. If the router's internal DNS cache becomes corrupted, its firmware has a bug, or it has been running for weeks without a restart, it can stop forwarding DNS queries correctly. Symptoms include DNS working on some devices but not others, or working intermittently. A simple power-cycle (unplug for 30 seconds, plug back in) fixes this surprisingly often.

3. Network Adapter Problems

The network adapter on your computer — whether Wi-Fi or Ethernet — can develop configuration issues that prevent DNS queries from being sent or received. Outdated or corrupted network drivers, a misconfigured static IP address, or a DHCP lease that has expired without renewal can all cause DNS failures on a single device even when other devices on the same network work perfectly.

4. Firewall or Antivirus Blocking DNS

Security software sometimes blocks or intercepts DNS traffic on UDP/TCP port 53. Some antivirus products redirect all DNS queries through their own filtering proxy, which can fail silently if the proxy crashes or is misconfigured. Third-party firewalls may have overly aggressive rules that drop outbound DNS packets. If DNS suddenly stops working after installing or updating security software, this is a likely culprit.

5. Incorrect DNS Settings

Manual DNS settings that were entered incorrectly, or DNS settings left over from a VPN that is no longer connected, can point your device at a DNS server that does not exist or is not reachable from your current network. This is especially common on laptops that move between home, office, and public Wi-Fi networks with different configurations.

6. Stale or Corrupted DNS Cache

Your operating system and browser both maintain a local DNS cache to speed up repeated lookups. If an entry in the cache becomes corrupted, points to an IP that no longer works, or conflicts with a recent DNS change (for example, after a website migrates servers), the cached data can cause resolution failures for specific domains or, in rare cases, prevent the DNS resolver from functioning correctly.

Step-by-Step Fixes for Windows

Windows 10 and Windows 11 share most of the same networking stack. The following fixes apply to both versions. Open Command Prompt as Administrator (right-click the Start button → Terminal (Admin) or search for "cmd" and select "Run as administrator") for all command-line steps.

Fix 1: Flush the DNS Cache

Flushing the DNS resolver cache is the single fastest thing you can try. It clears every cached DNS record on your machine and forces fresh lookups from the DNS server:

• Open Command Prompt as Administrator.
• Run: ipconfig /flushdns
• You should see: "Successfully flushed the DNS Resolver Cache."
• Try loading a website again in your browser.

If flushing alone does not resolve the issue, continue with the steps below — the cache flush eliminates one variable so subsequent fixes are more targeted.

Fix 2: Reset Winsock and the TCP/IP Stack

Winsock (Windows Sockets) is the interface that applications use to communicate over the network. Resetting it, along with the IP stack, repairs corruption in the networking configuration:

• netsh winsock reset — Resets the Winsock catalog to its default state.
• netsh int ip reset — Resets the TCP/IP stack by rewriting the relevant registry keys.
• ipconfig /release — Releases your current DHCP-assigned IP address.
• ipconfig /renew — Requests a new IP address and fresh DNS configuration from DHCP.
• Restart your computer after running these commands. The Winsock reset does not take full effect until reboot.

Fix 3: Change Your DNS Server to 1.1.1.1 or 8.8.8.8

Switching from your ISP's default DNS to a reliable public resolver is often an instant fix and a good long-term improvement for speed and reliability:

1. Open Settings → Network & Internet → click your active connection (Wi-Fi or Ethernet).
2. Click Hardware properties (Windows 11) or Properties (Windows 10).
3. Find DNS server assignment and click Edit.
4. Switch from "Automatic (DHCP)" to Manual.
5. Enable IPv4 and enter:
   • Preferred DNS: 1.1.1.1 (Cloudflare) or 8.8.8.8 (Google)
   • Alternate DNS: 1.0.0.1 (Cloudflare) or 8.8.4.4 (Google)
6. Click Save, then flush DNS with ipconfig /flushdns for good measure.

You can verify the change worked by running nslookup example.com in Command Prompt — the "Server" line should show the address you just configured.

Fix 4: Disable IPv6 DNS (If Applicable)

Some networks have partially broken IPv6 configurations where IPv6 DNS queries fail but IPv4 works fine. If your system tries IPv6 DNS first, it may time out before falling back to IPv4:

1. Open Control Panel → Network and Sharing Center → Change adapter settings.
2. Right-click your active adapter → Properties.
3. Uncheck Internet Protocol Version 6 (TCP/IPv6).
4. Click OK and test DNS resolution again.

If this fixes the issue, the problem is with your network's IPv6 DNS infrastructure. Contact your ISP or network administrator about IPv6 DNS support. Re-enable IPv6 later if your network is fixed, as disabling it permanently can cause issues with certain modern applications.

Fix 5: Run the Network Adapter Troubleshooter

Windows includes a built-in network diagnostics tool that can automatically detect and fix common adapter issues:

1. Open Settings → System → Troubleshoot → Other troubleshooters.
2. Click Run next to "Network & Internet" (Windows 11) or "Internet Connections" (Windows 10).
3. Follow the prompts. The troubleshooter will reset the adapter, re-acquire DHCP settings, and attempt DNS resolution.

The troubleshooter is not a magic bullet, but it handles a number of common misconfigurations automatically, such as a disabled adapter, a missing default gateway, or a corrupted DNS client service.

Fix 6: Update or Reinstall Network Drivers

Outdated or corrupted network drivers are a frequent but overlooked cause of DNS issues, especially after a Windows update:

1. Open Device Manager (right-click Start → Device Manager).
2. Expand Network adapters.
3. Right-click your Wi-Fi or Ethernet adapter → Update driver → Search automatically for drivers.
4. If no update is found, visit your adapter manufacturer's website (Intel, Realtek, Qualcomm, etc.) and download the latest driver manually.
5. As a last resort, right-click the adapter → Uninstall device (check "Delete the driver software"), then restart. Windows will reinstall a fresh default driver on boot.

Step-by-Step Fixes for Mac

macOS uses its own DNS resolution stack. The following steps apply to macOS Ventura, Sonoma, Sequoia, and later versions using System Settings (the older System Preferences UI is functionally equivalent for DNS settings).

Fix 1: Flush the DNS Cache

macOS caches DNS records through the mDNSResponder daemon. Flushing it forces fresh lookups:

• Open Terminal (Applications → Utilities → Terminal).
• Run: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
• Enter your administrator password when prompted.
• There is no confirmation message — if the command completes without error, the cache has been flushed.

Fix 2: Renew the DHCP Lease

Renewing the DHCP lease forces your Mac to request a fresh IP address and DNS server configuration from the router:

1. Open System Settings → Network → click your active connection (Wi-Fi or Ethernet).
2. Click Details → TCP/IP tab.
3. Click Renew DHCP Lease.
4. Try loading a website again.

Fix 3: Change DNS Servers in System Settings

Switching to a public DNS resolver is the most reliable long-term fix on Mac:

1. Open System Settings → Network → click your active connection.
2. Click Details → DNS tab.
3. Click the + button to add a new DNS server. Remove any existing entries provided by DHCP (they will be greyed out; click − to remove them if editable, or they will be overridden by manual entries).
4. Add 1.1.1.1 and 1.0.0.1 (Cloudflare), or 8.8.8.8 and 8.8.4.4 (Google).
5. Click OK, then Apply.

Verify the change by running dig example.com in Terminal — the ;; SERVER: line in the output should show the DNS address you configured.

Step-by-Step Fixes for Linux

Linux DNS configuration varies depending on your distribution and whether you use systemd-resolved, NetworkManager, or manual /etc/resolv.conf management. Here are fixes for each approach.

Fix 1: Flush the DNS Cache (systemd-resolved)

Most modern Ubuntu, Fedora, and Arch-based distributions use systemd-resolved as the local DNS stub resolver. It maintains its own cache:

• Flush the cache: sudo resolvectl flush-caches
• Verify it was flushed: resolvectl statistics — the cache size should be 0.
• Check current DNS configuration: resolvectl status — this shows which DNS servers are configured for each network interface.

Fix 2: Change DNS via NetworkManager

If you use NetworkManager (default on Ubuntu Desktop, Fedora Workstation, and most desktop distributions):

• GUI method: Open Settings → Network (or Wi-Fi) → click the gear icon on your active connection → IPv4 tab → set DNS to 1.1.1.1, 1.0.0.1 and toggle off "Automatic" for DNS.
• CLI method: nmcli con mod "Your Connection Name" ipv4.dns "1.1.1.1 1.0.0.1" followed by nmcli con mod "Your Connection Name" ipv4.ignore-auto-dns yes and nmcli con up "Your Connection Name".

Fix 3: Edit /etc/resolv.conf Directly

On minimal server installations or distributions without systemd-resolved, DNS is configured directly in /etc/resolv.conf:

• Open the file: sudo nano /etc/resolv.conf
• Replace or add nameserver lines:
  • nameserver 1.1.1.1
  • nameserver 1.0.0.1
• Save and exit. DNS changes take effect immediately — no restart is needed.

Important: On systems using systemd-resolved or NetworkManager, /etc/resolv.conf is often a symlink that gets overwritten. Edit DNS through the service that manages it (steps above) rather than editing the file directly, or your changes will be lost on the next network event.

Fix 4: Restart the DNS Resolver Service

If the local resolver has hung or entered a bad state, restarting it can restore DNS:

• systemd-resolved: sudo systemctl restart systemd-resolved
• NetworkManager: sudo systemctl restart NetworkManager
• Verify resolution: dig example.com or nslookup example.com

Router-Level Fixes

If multiple devices on your network are experiencing DNS failures, the problem is almost certainly at the router or ISP level rather than on individual devices. These fixes address network-wide DNS issues.

Reboot Your Router and Modem

This is the simplest and most effective router-level fix. Consumer routers run a small embedded OS that can develop memory leaks, cache corruption, and other issues over time:

1. Unplug the power cable from your modem (the device your ISP provided) and your router (if they are separate devices).
2. Wait 30 seconds. This ensures capacitors fully discharge and volatile memory is cleared.
3. Plug the modem back in first. Wait for it to fully connect (all indicator lights should stabilize — this can take 1–2 minutes).
4. Plug the router back in and wait for it to boot and re-establish the Wi-Fi network.
5. Test DNS resolution on your devices.

Change DNS Servers on the Router

Changing DNS at the router level means every device on your network automatically uses the new DNS servers without needing individual configuration:

1. Open your router's admin panel by navigating to 192.168.1.1 or 192.168.0.1 in your browser (check the sticker on your router for the exact address and default credentials).
2. Navigate to WAN, Internet, or DHCP settings (the exact location varies by router brand).
3. Find the DNS server fields. They may be labeled "Primary DNS" and "Secondary DNS" or "DNS 1" and "DNS 2."
4. Enter 1.1.1.1 and 1.0.0.1 (Cloudflare) or 8.8.8.8 and 8.8.4.4 (Google).
5. Save the settings. The router may reboot automatically.

Update Router Firmware

Outdated router firmware can contain bugs that cause DNS resolution failures, especially when handling large volumes of queries or DNSSEC-signed responses:

1. Log into your router's admin panel.
2. Look for a Firmware Update, System Update, or Router Update section (usually under Administration or System).
3. Check for updates and install any available firmware. The router will reboot during the update — do not unplug it during this process.
4. After the update, verify your DNS and Wi-Fi settings are still correct (some firmware updates reset settings to defaults).

Browser-Specific DNS Errors

Browsers display DNS failures with their own specific error codes. Understanding what each code means helps you determine whether the problem is DNS-related or something else entirely.

DNS_PROBE_FINISHED_NXDOMAIN

This Chrome/Edge error means the DNS server was reached and responded that the domain name does not exist (NXDOMAIN — Non-Existent Domain). Unlike "DNS Server Not Responding," this error confirms DNS is working but the specific domain cannot be found. Common causes:

• Typo in the URL — Double-check the domain name for misspellings.
• Expired domain — The website owner may not have renewed their domain registration.
• DNS propagation — If the domain was recently registered or moved to a new DNS provider, it can take up to 48 hours for records to propagate globally.
• Local hosts file redirect — Check your hosts file (C:\Windows\System32\drivers\etc\hosts on Windows, /etc/hosts on Mac/Linux) for entries that may be overriding DNS for that domain.

ERR_NAME_NOT_RESOLVED

This is a more generic Chrome/Edge error indicating that the domain name could not be resolved. It can appear when the DNS server is unreachable, when the domain does not exist, or when there is a network connectivity issue preventing the DNS query from completing. The troubleshooting steps in this guide address all of these scenarios.

Firefox: "Hmm. We're having trouble finding that site."

Firefox uses its own DNS resolution in some configurations, including DNS-over-HTTPS (DoH) via Cloudflare by default in certain regions. If Firefox cannot resolve a domain but Chrome can (or vice versa), check Firefox's DNS settings:

1. Open Settings → search for DNS.
2. Under "DNS over HTTPS," try switching between "Default Protection," "Increased Protection," "Max Protection," and "Off" to see which setting resolves the issue.
3. If Max Protection mode is on and the DNS-over-HTTPS provider is unreachable, Firefox will not fall back to system DNS — it will simply fail. Switching to "Default Protection" or "Off" allows fallback.

Clearing Browser DNS Cache

Browsers maintain their own DNS cache separate from the operating system's cache. If you've flushed the OS cache but a specific domain still fails, clear the browser's cache too:

• Chrome/Edge: Navigate to chrome://net-internals/#dns (or edge://net-internals/#dns) and click Clear host cache.
• Firefox: Navigate to about:networking#dns and click Clear DNS Cache.
• Safari: Go to Develop menu → Empty Caches (enable the Develop menu in Safari → Settings → Advanced first).

Advanced Diagnostics with nslookup and dig

When the basic fixes do not resolve the issue, or when you need to understand exactly where DNS is failing, command-line diagnostic tools provide detailed information about every step of the resolution process.

Using nslookup (Windows, Mac, Linux)

nslookup is available on every major operating system and is the go-to tool for quick DNS diagnostics:

• nslookup example.com — Queries your default DNS server for the domain. The output shows the server used and the resolved IP addresses.
• nslookup example.com 1.1.1.1 — Queries Cloudflare's DNS specifically. If this works but the default server query fails, your configured DNS server is the problem.
• nslookup -type=MX example.com — Queries a specific record type (MX for mail servers, NS for nameservers, TXT for text records, AAAA for IPv6).
• nslookup -debug example.com — Shows detailed query and response information, including TTL values and intermediate steps.

Using dig (Mac, Linux)

dig (Domain Information Groper) provides more detailed output than nslookup and is preferred by network administrators for troubleshooting:

• dig example.com — Performs a standard A record query and shows the full response, including the query time, server used, and all returned records.
• dig @1.1.1.1 example.com — Queries a specific DNS server. The @ symbol specifies the server to use.
• dig example.com +trace — Traces the full resolution path from the root DNS servers down to the authoritative nameserver. This reveals exactly where in the DNS hierarchy a failure occurs.
• dig example.com +short — Returns only the answer (IP address) without additional information. Useful for scripting.
• dig example.com ANY — Requests all record types for the domain (A, AAAA, MX, NS, TXT, etc.).

Diagnostic Workflow

Use this systematic approach to narrow down DNS problems:

1. Test with your default DNS: Run nslookup example.com. If it fails, note the error.
2. Test with a public DNS: Run nslookup example.com 1.1.1.1. If this works, your configured DNS server is the issue — switch to a public DNS.
3. Test raw connectivity: Run ping 1.1.1.1. If the ping fails, you have a network connectivity problem, not a DNS problem.
4. Test a different domain: Run nslookup google.com. If google.com resolves but your target domain does not, the issue is with that specific domain's DNS records, not your DNS configuration.
5. Trace the resolution: Run dig example.com +trace to find exactly where resolution breaks down — root servers, TLD servers, or authoritative nameservers.

For a quick visual check, try our DNS Lookup tool — it queries multiple DNS record types from our infrastructure and displays the results instantly.

Preventing DNS Issues in the Future

Once you've fixed the immediate problem, these practices help prevent "DNS Server Not Responding" from recurring:

• Use a reliable public DNS resolver permanently. Set 1.1.1.1 (Cloudflare) or 8.8.8.8 (Google) on your router so all devices benefit. Both services have multi-region redundancy and near-perfect uptime.
• Configure a secondary DNS server. Always set both a preferred and alternate DNS address. If the primary fails, your device will automatically fall back to the secondary.
• Restart your router monthly. A scheduled reboot clears the router's internal caches and frees memory, preventing the gradual accumulation of issues.
• Keep network drivers and router firmware up to date. Manufacturers release patches that fix DNS-related bugs. Enable automatic updates where possible.
• Use DNS-over-HTTPS (DoH) or DNS-over-TLS (DoT). Encrypted DNS prevents ISP interference and middlebox tampering that can cause spurious DNS failures. Windows 11, macOS, iOS, Android, and all major browsers support encrypted DNS natively.
• Avoid security software that hijacks DNS. If your antivirus or firewall intercepts DNS queries, make sure its DNS filtering feature is properly maintained and updated. Consider using a DNS-level filtering service like 1.1.1.1 for Families instead.

Frequently Asked Questions

What does "DNS Server Not Responding" mean?

It means your device sent a DNS query to translate a domain name into an IP address, but the DNS server did not reply within the timeout period. This prevents your browser from locating the website's server. Your internet connection may still be working — only name resolution is broken.

How do I flush my DNS cache on Windows?

Open Command Prompt as Administrator and run ipconfig /flushdns. You'll see a confirmation message saying "Successfully flushed the DNS Resolver Cache." This clears all cached DNS entries and forces fresh lookups.

How do I change my DNS server to 1.1.1.1 or 8.8.8.8?

On Windows, go to Settings → Network & Internet → your connection → DNS server assignment → Edit, switch to Manual, and enter 1.1.1.1 (preferred) and 1.0.0.1 (alternate). On Mac, go to System Settings → Network → your connection → Details → DNS and add the addresses. On Linux, edit via nmcli or your /etc/resolv.conf file.

Why does my DNS work on one device but not another?

If DNS fails on one device but works on others sharing the same network, the issue is device-specific. Common causes include a corrupted local DNS cache, incorrect DNS settings, outdated network drivers, or firewall software blocking DNS queries on that device. Try flushing the DNS cache and resetting the network adapter.

What is the difference between DNS_PROBE_FINISHED_NXDOMAIN and DNS server not responding?

DNS_PROBE_FINISHED_NXDOMAIN means the DNS server was reached and replied that the domain does not exist. "DNS Server Not Responding" means no DNS server replied at all. NXDOMAIN usually indicates a typo or expired domain; "not responding" points to a network or DNS server availability issue.

How do I fix DNS issues on my router?

Start by rebooting the router (unplug for 30 seconds). If the problem persists, log into the admin panel and change the DNS servers to 1.1.1.1/1.0.0.1 or 8.8.8.8/8.8.4.4. Also check for firmware updates, as outdated firmware can cause DNS resolution failures.

Can antivirus or firewall software cause DNS errors?

Yes. Security software can block DNS traffic on port 53, intercept queries for web filtering, or inject its own DNS settings that fail silently. Temporarily disable your security software to test. If DNS works with it disabled, add an exception for DNS traffic or use the software's built-in DNS filtering mode.

How do I use nslookup or dig to diagnose DNS problems?

Run nslookup example.com (all platforms) or dig example.com (Mac/Linux) to test DNS resolution. To query a specific DNS server, use nslookup example.com 1.1.1.1 or dig @1.1.1.1 example.com. If the query works against a public DNS but fails with your default server, switch your DNS configuration.