What does DNS server not responding mean?

DNS server not responding means your device tried to contact a DNS server to resolve a domain name but received no response. This can happen if the DNS server is down, your network connection is blocked, or your device's DNS settings point to an unreachable server.

How do I fix DNS_PROBE_FINISHED_NO_INTERNET?

This Chrome error means DNS resolution succeeded but the device cannot reach the internet. Try flushing your DNS cache, restarting your router, disabling VPNs, or changing to a public DNS server like Cloudflare 1.1.1.1 or Google 8.8.8.8.

Will changing my DNS server fix most errors?

Yes. Many DNS errors are caused by slow or unreliable ISP DNS servers. Switching to a public DNS provider like Cloudflare, Google, or Quad9 resolves most DNS-related errors immediately.

DNS Errors Troubleshooting — Fix DNS Server Not Responding

DNS errors are among the most frustrating internet problems. You know your internet works — other apps show connected status — but your browser says the server cannot be found. The page does not load. You get a cryptic error message that means nothing to you.

I have spent years helping people debug these exact issues. The good news is that most DNS errors are easy to fix. You do not need to be a network engineer. In most cases, the solution takes less than five minutes and involves changing one setting or running one command.

This guide covers every major DNS error you might encounter. I explain what each error means, why it happens, and exactly how to fix it on Windows, Mac, Android, iOS, and your router.

DNS Server Not Responding

This is the most common DNS error. Windows shows it as "DNS server not responding" in the network troubleshooter. Your browser cannot load any websites, but other network services might still work.

The error means your device sent a DNS query to the configured DNS server but got no reply. The server could be down, overloaded, or unreachable due to a network problem. ISP DNS servers fail more often than most people realize. When thousands of customers in the same area pound the same DNS server, it can fall over.

How to Fix It

First, try a different DNS server. This is the fastest fix. Open your network settings and change the DNS server to 1.1.1.1 (Cloudflare) or 8.8.8.8 (Google). If you are on Windows, go to Network and Sharing Center, click your connection, open Properties, select Internet Protocol Version 4, and enter the new DNS addresses manually.

If changing DNS does not work, restart your router. Unplug it for thirty seconds, plug it back in, and wait two minutes for it to come back online. Router firmware can develop DNS forwarding issues over time. A clean restart flushes those problems.

Flush your DNS cache too. On Windows, open Command Prompt as administrator and run ipconfig /flushdns. On Mac, run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder.

DNS_PROBE_FINISHED_NO_INTERNET

This Chrome-specific error is confusing. The error says "no internet," but your Wi-Fi shows connected. What actually happened is that Chrome resolved the domain name successfully, tried to connect to the server, and failed. The DNS lookup worked. The connection to the site did not.

This usually means one of three things: your network has connectivity issues beyond DNS, a VPN or proxy is interfering, or your DNS cache is corrupted. The error is Chrome's way of saying "I found the address, but nobody answered the door."

How to Fix It

Start by disabling any VPN or proxy software. Virtual private networks and web proxies reroute your traffic through their own DNS resolvers. If the VPN server has DNS issues, you get this error. Turn off the VPN and test again.

Next, flush your DNS cache and renew your IP address. On Windows, run ipconfig /flushdns followed by ipconfig /release and ipconfig /renew. This gives your network adapter a fresh lease and clears any stale DNS entries.

If the problem persists, reset Chrome's network settings. Go to chrome://net-internals/#dns and click "Clear host cache." You can also try using Chrome's built-in cleanup tool at chrome://settings/cleanup.

DNS Lookup Failed / DNS_PROBE_FINISHED_NXDOMAIN

This error means the DNS server responded, but it said the domain does not exist. The server returned NXDOMAIN — non-existent domain. If you are sure the website exists, there is a problem with your DNS resolution chain.

The most common cause is a bad DNS cache entry. Your computer cached an old response that says the domain does not exist, even though the domain was registered or reactivated since then. This happens frequently with recently registered domains or after website migrations.

How to Fix It

Flush your DNS cache first. On Windows: ipconfig /flushdns. On Mac: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. On Linux: sudo systemctl restart nscd or sudo systemctl restart systemd-resolved.

If flushing the cache does not work, try a different DNS resolver. Your ISP's DNS server might have outdated information. Switch to Cloudflare 1.1.1.1 or Google 8.8.8.8 temporarily and see if the domain resolves. If it does, the problem is with your original DNS provider, not your computer.

You can check if the domain actually exists using our DNS lookup tool. Enter the domain and see what records come back. If a public resolver finds the domain but your ISP's resolver does not, it is time to switch DNS providers permanently.

ERR_CONNECTION_REFUSED

ERR_CONNECTION_REFUSED means the DNS resolution succeeded — the domain was translated to an IP address successfully — but the server at that IP address actively refused the connection. The server is running, but it is not accepting connections on the port your browser requested.

This is usually not a DNS problem. It means the website's server is down, overloaded, or blocking your IP address. However, DNS misconfigurations can sometimes cause this error. If a domain recently changed IP addresses and your DNS cache still points to the old server, that old server might refuse connections.

How to Fix It

Clear your browser cache and DNS cache. If the site just migrated to a new server, your computer might still be trying the old IP address. Run ipconfig /flushdns on Windows or the equivalent on your OS, then restart your browser.

Check if the website is down for everyone using a service like downforeveryoneorjustme.com. If the site is down globally, the problem is on their end. If it is just you, try disabling your firewall temporarily to see if it is blocking the connection.

DNS Errors by Device

Windows

Windows users see DNS errors most often. The built-in network troubleshooter usually detects them but rarely fixes them. The most effective Windows fix is running the command prompt as administrator and executing: ipconfig /flushdns, ipconfig /registerdns, ipconfig /release, ipconfig /renew, netsh winsock reset. Run them in that order and restart your computer.

Mac

Mac DNS errors typically come from corrupted DNS caches. The fix is straightforward even if the terminal command looks intimidating. Open Terminal and run: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. You will need to enter your password. This clears the mDNSResponder cache, which is the process handling DNS on macOS.

Android

Android DNS errors are usually fixed by switching from automatic DNS to a private DNS provider. Go to Settings, then Network & Internet, then Private DNS. Select "Private DNS provider hostname" and enter one.one.one.one or dns.google. This forces all DNS queries through DNS over TLS, bypassing your ISP's potentially broken DNS servers.

iOS

On iPhone and iPad, DNS errors often come from bad Wi-Fi configurations. The easiest fix is to forget the Wi-Fi network and reconnect. Go to Settings, Wi-Fi, tap the info icon next to your network, and select "Forget This Network." Reconnect and enter the password. If the problem persists, change your DNS to 1.1.1.1 or 8.8.8.8 in the Wi-Fi settings.

Routers

Router-level DNS errors affect every device on your network. Log into your router's admin panel, find the DNS settings (usually under WAN or Internet settings), and change from ISP default to a public DNS provider. After saving, reboot the router. This fixes DNS errors for every phone, laptop, and tablet in your home at once.

How to Prevent DNS Errors

Preventing DNS errors is easier than fixing them. The single most effective step is switching away from your ISP's default DNS servers. ISP DNS servers are notoriously unreliable because they are under-provisioned and not prioritized for performance. Public DNS providers like Cloudflare, Google, and Quad9 run massive global infrastructure designed to handle millions of queries per second.

Use reliable DNS servers on your router. This fixes DNS for every device on your network. You do not need to configure each phone and laptop individually. Set it once on the router and all devices benefit.

Keep your router firmware updated. Router manufacturers release firmware updates that fix DNS forwarding bugs and security vulnerabilities. Check for updates every few months.

Consider using encrypted DNS. DNS over HTTPS and DNS over TLS are more resilient to tampering and less likely to suffer from ISP-level DNS failures. Most modern operating systems support encrypted DNS natively. Android has Private DNS built in. Windows supports DoH starting from Windows 10. macOS supports DoT and DoH natively.

Run our DNS speed test periodically to check your current DNS performance. If your resolver starts showing high latency or packet loss, it is a warning sign that problems are coming.