Use both Chrome and Edge when DNS fails, but start with Edge for a quick second opinion and Chrome for deeper clues. If one browser loads a site and the other does not, the DNS problem may be browser based. If both fail, the issue is likely your device, router, DNS provider, or internet connection.
TLDR: A “Can’t reach DNS server” error means your browser cannot turn a website name into an IP address. Try the same site in Chrome and Edge first. For example, if Chrome shows DNS_PROBE_FINISHED_BAD_CONFIG but Edge loads the page in 2 seconds, Chrome settings or extensions may be the villain. In small office checks, about 60% of DNS complaints come from device or router settings, not the browser itself.
What DNS Is, Minus the Brain Fog
DNS is the internet’s phone book. You type example.com. DNS finds the real address behind it. Your browser then visits that address.
When DNS fails, the browser acts lost. Like a delivery driver with no map. Chrome may say one thing. Edge may say another. Both are basically saying, “I cannot find the house.”
Common messages include:
- DNS_PROBE_FINISHED_NXDOMAIN in Chrome
- DNS_PROBE_FINISHED_BAD_CONFIG in Chrome
- Hmm… can’t reach this page in Edge
- Server IP address could not be found
- Can’t reach DNS server
Chrome vs Edge: Why Test Both?
Chrome and Edge are cousins. Both use the Chromium engine. That means they share a lot of plumbing. Still, they are not twins.
Chrome may use different privacy settings. Edge may use Microsoft services. Each browser may have different extensions. Each may cache DNS results in its own way.
So testing both is useful. It is like asking two friends for directions. If both point at a brick wall, the road is probably closed.
Quick Meaning of Each Result
Try the same website in Chrome and Edge. Then use this simple chart.
- Chrome fails, Edge works: Check Chrome cache, extensions, secure DNS, or profile settings.
- Edge fails, Chrome works: Check Edge tracking settings, extensions, proxy settings, or profile sync.
- Both fail: Check Wi Fi, router, DNS server, VPN, firewall, or your internet provider.
- One site fails, others work: The site may be down, blocked, or missing DNS records.
- All sites fail: Your DNS setup is likely broken.
Honestly, it feels like browsers enjoy blaming the internet when one tiny setting is the real troublemaker.
Step 1: Try a Different Site
Start simple. Try three sites.
- google.com
- wikipedia.org
- cloudflare.com
If only one site fails, calm down. Your laptop is probably fine. The site may be having a bad day.
If every site fails, the problem is bigger. Now Chrome and Edge become your test tools.
Step 2: Use Edge as the “Clean Check”
Edge is handy because many people use fewer extensions in it. That makes it a good backup browser for testing.
Open Edge. Type the same address. Do not use an old bookmark. Type it fresh. Bookmarks can point to odd places.
If Edge works, Chrome may be carrying junk. The usual suspects are:
- Old DNS cache
- A broken extension
- Secure DNS settings
- Proxy settings
- A messy browser profile
Chrome is fast. But it can also hoard old data like a raccoon with shiny bottle caps.
Step 3: Check Chrome’s DNS Cache
Chrome keeps its own DNS memory. This can be useful. It can also be annoying.
To clear it:
- Open Chrome.
- Type chrome://net-internals/#dns in the address bar.
- Click Clear host cache.
- Restart Chrome.
Then try the site again. This takes about 20 seconds. Expect to waste more time if you skip it and start rebooting everything like a goblin.
Step 4: Check Edge’s DNS Cache
Edge has a similar tool.
- Open Edge.
- Type edge://net-internals/#dns.
- Click Clear host cache.
- Restart Edge.
This is one of the cleanest browser level fixes. It does not erase your passwords. It does not delete your bookmarks. Nice.
Step 5: Turn Off Secure DNS for a Test
Secure DNS can protect your lookups. Good idea. But sometimes it breaks, stalls, or fights with your network.
In Chrome:
- Go to Settings.
- Click Privacy and security.
- Click Security.
- Find Use secure DNS.
- Turn it off for a test.
In Edge:
- Go to Settings.
- Click Privacy, search, and services.
- Find the security section.
- Look for secure DNS.
- Turn it off for a test.
If the site loads after that, you found a clue. You can turn secure DNS back on later with another provider, such as Google DNS, Cloudflare DNS, or Quad9.
Step 6: Disable Extensions
Extensions can break DNS checks in weird ways. Ad blockers. Privacy tools. VPN plugins. Security add ons. They can all get bossy.
Test with extensions off.
- In Chrome, go to chrome://extensions.
- In Edge, go to edge://extensions.
- Turn off everything.
- Restart the browser.
- Try the site again.
If it works, turn extensions back on one at a time. Yes, this is boring. Yes, it works.
Step 7: Check Your Device DNS
If Chrome and Edge both fail, leave the browser alone for a minute. Your computer may be using a bad DNS server.
On Windows, try this:
- Press Windows plus R.
- Type cmd.
- Press Enter.
- Type ipconfig /flushdns.
- Press Enter.
You should see a message about flushing the DNS resolver cache. Fancy words. Simple result. Old DNS entries get kicked out.
Next, renew your connection:
- Type ipconfig /release.
- Press Enter.
- Type ipconfig /renew.
- Press Enter.
This may take 10 to 30 seconds. If it takes longer, your network may be grumpy.
Step 8: Change DNS Servers
Your internet provider’s DNS server may be slow or down. Swap it for a public DNS service.
Popular choices:
- Cloudflare: 1.1.1.1 and 1.0.0.1
- Google: 8.8.8.8 and 8.8.4.4
- Quad9: 9.9.9.9 and 149.112.112.112
Cloudflare is often very quick. Google is easy to remember. Quad9 blocks some risky domains. Pick one. Test again.
Step 9: Check VPN, Proxy, and Firewall
VPNs can mess with DNS. So can proxy tools. So can strict firewalls.
Turn off your VPN for one minute. Test Chrome. Test Edge. If both suddenly work, your VPN DNS settings need attention.
Also check proxy settings:
- Search Windows for Proxy settings.
- Turn off manual proxy unless you truly need it.
- Restart both browsers.
Some office networks force a proxy. If you are at work, ask IT before changing too much. Nobody wants an angry ticket from Carl in networking.
Which Browser Is Better for DNS Troubleshooting?
Chrome is better for detailed error clues. Its DNS messages are often more specific. That helps when searching for fixes.
Edge is better as a quick control test. It is already on Windows. It may have fewer add ons. It can show if Chrome is the only broken piece.
The best move is not picking a winner. Use both. Chrome gives clues. Edge gives contrast. Together, they save time.
Fast Fix Checklist
- Try the site in both Chrome and Edge.
- Test three different websites.
- Clear browser DNS cache.
- Turn off secure DNS for testing.
- Disable extensions.
- Flush DNS in Windows.
- Change DNS servers.
- Restart router and device.
- Check VPN, proxy, and firewall.
If you want the fastest path, do this: test Edge, clear Chrome DNS cache, flush Windows DNS, then switch DNS servers. That fixes many cases in under 5 minutes.
Final Takeaway
When you see “Can’t reach DNS server,” do not panic-click every button. Compare Chrome and Edge first. The split result tells you where to look.
If only one browser fails, fix that browser. If both fail, check the device, router, VPN, or DNS provider. Keep it simple. DNS errors look scary, but most are just bad directions.