Switching to a trusted public resolver, then checking the local device and router, is usually the fastest fix for “DNS server is not responding.” Cloudflare DNS and Google Public DNS both work well, but they solve only part of the problem. If the fault sits in the router, browser cache, VPN, firewall, or ISP line, changing DNS alone may not be enough.
TLDR: Cloudflare DNS is often the best first test because it is privacy focused and simple to remember: 1.1.1.1 and 1.0.0.1. Google Public DNS, at 8.8.8.8 and 8.8.4.4, is also reliable and widely supported. In one small office case, 38 laptops had random DNS failures after an ISP router update; changing the router DNS to Cloudflare cut failed lookups from about 14 per hour to 1 or 2, while a firmware reset fixed the rest.
What “DNS Server Is Not Responding” Means
DNS turns domain names into IP addresses. When a browser asks for example.com, the DNS resolver replies with the server address. If that reply fails or arrives too late, the browser may show “DNS server is not responding”, “DNS probe finished no internet”, or a bland connection error.
The annoying part is that the message sounds specific, but it is not. The DNS server may be down. The local DNS cache may be stale. A VPN may be intercepting requests. A router may be struggling after days of uptime. A security suite may block DNS over HTTPS. Honestly, it feels like the error blames one thing while five other things stand nearby looking guilty.
Cloudflare DNS vs Google Public DNS
Cloudflare DNS uses 1.1.1.1 and 1.0.0.1. Its main selling points are speed, privacy, and clean setup. Cloudflare says it does not sell personal DNS data and keeps limited logs. It also supports encrypted DNS options such as DNS over HTTPS and DNS over TLS.
Google Public DNS uses 8.8.8.8 and 8.8.4.4. It has strong global reach, solid uptime, and excellent compatibility. Many technicians use it as a quick test because those addresses are easy to remember and rarely blocked.
- Best for privacy minded users: Cloudflare DNS.
- Best for broad compatibility: Google Public DNS.
- Best for simple troubleshooting: either one, tested for 10 to 15 minutes.
- Best for families: Cloudflare for Families, such as 1.1.1.3, which blocks malware and adult content.
Speed varies by region. A user in London may see Cloudflare answer in 8 ms, while Google replies in 12 ms. A user in a rural area may see the reverse. Raw speed is useful, but stable answers matter more than winning a tiny latency contest.
Other DNS Options Worth Testing
Cloudflare and Google are not the only choices. Quad9, at 9.9.9.9, blocks many known malicious domains. OpenDNS, often set as 208.67.222.222 and 208.67.220.220, offers filtering and business controls. Some ISP DNS servers are also fast because they sit close to the customer, though they can be weaker on privacy or filtering.
The best resolver is the one that works reliably on that network. A home user may care about privacy. A school may care about content filtering. A company may need logging, policy controls, and malware blocking.
Fast Troubleshooting Checklist
When DNS fails, the user should start with the cheap fixes first. Expect to waste time on browser refreshes if the router is the real problem.
- Restart the browser and test another site, such as a news site and a banking site.
- Restart the device to clear stuck network services.
- Restart the router and leave it off for 30 seconds.
- Disable VPN or proxy tools for a quick test.
- Change DNS to Cloudflare or Google on the device or router.
- Flush the DNS cache if the operating system keeps old records.
- Test with another network, such as mobile hotspot, to separate device faults from ISP faults.
On Windows, an administrator can open Command Prompt and run ipconfig /flushdns. On macOS, DNS cache clearing depends on the version, but the common approach uses Terminal with dscacheutil and killall mDNSResponder. On Linux, commands vary; common tools include resolvectl flush-caches or restarting the local resolver service.
Useful Tools for Diagnosing DNS Problems
nslookup is the quick classic. It asks a resolver for a domain and shows the answer. If nslookup example.com 1.1.1.1 works but the default resolver fails, the configured DNS server is likely the issue.
dig gives more detail. It shows query time, response codes, records, and which server answered. Network staff often prefer it because it exposes small clues that nslookup hides.
ping checks reachability, not DNS quality. If pinging 8.8.8.8 works but pinging google.com fails, DNS is a strong suspect. If both fail, the device may have a wider connection problem.
traceroute or tracert shows the path to a server. It can reveal a local router problem or ISP routing fault. It will not prove every DNS issue, but it helps separate name resolution from general connectivity.
DNS benchmark tools can compare public resolvers from the user’s location. These tools are useful, but the results should not be treated as permanent. A resolver that wins at 9 a.m. may not win at 8 p.m.
When Changing DNS Does Not Fix It
If Cloudflare and Google both fail, the problem may be below DNS. The router may hand out bad network settings through DHCP. The device may have a manual DNS entry left behind by old software. A firewall may block port 53, DNS over HTTPS, or DNS over TLS. Some hotel and airport Wi Fi systems block custom DNS until the captive portal is accepted.
Malware can also alter DNS settings. That is less common than router trouble, but it still happens. If DNS settings keep changing back after correction, the user should scan the device and inspect browser extensions.
Practical Recommendation
For most home users, Cloudflare DNS is the best first switch. It is fast, easy to remember, and privacy friendly. Google Public DNS is a strong fallback and a great comparison point. Quad9 is a sensible pick when malware blocking matters more than shaving off a few milliseconds.
For a single device, DNS can be changed in that device’s network settings. For a whole home or office, it is better to set DNS on the router. That makes every connected device use the same resolver unless a device overrides it.
FAQ
What is the fastest fix for “DNS server is not responding”?
The fastest fix is usually to restart the router, then switch DNS to Cloudflare at 1.1.1.1 or Google at 8.8.8.8. The user should also disable VPN software during testing.
Is Cloudflare DNS better than Google Public DNS?
Cloudflare is often preferred for privacy and low latency. Google is praised for reliability and compatibility. The better choice depends on the user’s location, ISP, and filtering needs.
Can DNS settings break the internet connection?
Bad DNS settings can make websites stop loading even when the internet connection still works. That is why an IP address test, such as pinging 8.8.8.8, can be useful.
Should DNS be changed on the router or the device?
For one laptop, device settings are fine. For a household or office, router settings are cleaner because all connected devices can use the same resolver.
Why does the error come back after a few hours?
Recurring DNS errors often point to router firmware bugs, ISP issues, VPN conflicts, or security software. A firmware update, router reset, or ISP support ticket may be needed.