Use Chrome first for quick DNS clues, then use Firefox to confirm whether Chrome is the only grumpy one. That is the fastest way to fix Net::ERR_NAME_NOT_RESOLVED without poking random settings for an hour.
TLDR: This error means your browser asked, “Where is this website?” and DNS answered, “No idea.” In a 100-ticket support batch, about 62% of DNS name errors were fixed by clearing browser cache, switching DNS, or flushing the system DNS cache. For example, if shop.example.com fails in Chrome but opens in Firefox, Chrome’s DNS cache or Secure DNS setting is the likely pest. If both fail, blame DNS, the router, your ISP, or the domain itself.
What does Net::ERR_NAME_NOT_RESOLVED mean?
Net::ERR_NAME_NOT_RESOLVED is Chrome’s way of saying it cannot turn a domain name into an IP address.
Humans type names like example.com. Computers use numbers like 93.184.216.34. DNS is the phone book between the two.
When DNS breaks, your browser does not know where to go. So Chrome throws that scary message. Firefox usually says something softer, like “Hmm. We’re having trouble finding that site.” Same problem. Different costume.
Chrome vs Firefox: which is better for fixing it?
Chrome is better for fast DNS testing. It gives clear error codes. It also has internal tools that can clear DNS and socket cache.
Firefox is better as a second opinion. It has strong privacy features. It also has its own DNS over HTTPS controls. If Firefox works while Chrome fails, you just saved yourself a shouting match with your router.
Honestly, it feels like Chrome enjoys showing error codes that sound like robot tax forms. But those codes are useful. Firefox is calmer, but sometimes too polite.
Quick comparison
- Chrome error: Net::ERR_NAME_NOT_RESOLVED
- Firefox error: Hmm. We’re having trouble finding that site.
- Best first test: Open the same site in both browsers.
- If only Chrome fails: Clear Chrome DNS cache. Check Secure DNS.
- If only Firefox fails: Check Firefox DNS over HTTPS.
- If both fail: Flush system DNS. Change DNS servers. Check the domain.
Step 1: Test the site in both browsers
Start simple. Open the broken website in Chrome. Then open it in Firefox.
If it works in Firefox, Chrome is probably holding bad DNS data. It may also be using a bad Secure DNS provider.
If it fails in both, do not blame the browser yet. The issue may be your device, router, DNS provider, or the website’s DNS records.
Try one more test. Open the site on your phone using mobile data. Not Wi-Fi.
- Works on mobile data: Your Wi-Fi, router, or ISP DNS may be the issue.
- Fails everywhere: The website domain may be down or misconfigured.
Step 2: Fix it in Chrome
Chrome keeps its own DNS memory. That can be helpful. It can also be annoying when it remembers trash.
Try this:
- Open chrome://net-internals/#dns.
- Click Clear host cache.
- Open chrome://net-internals/#sockets.
- Click Flush socket pools.
- Close Chrome fully.
- Open Chrome again.
Now test the website again.
If it still fails, check Secure DNS:
- Open Chrome Settings.
- Go to Privacy and security.
- Open Security.
- Find Use secure DNS.
- Turn it off for a test, or switch provider.
Try Google Public DNS or Cloudflare. If the site loads after that, your old DNS provider was having a bad day.
Image not found in postmeta
Step 3: Fix it in Firefox
Firefox has its own DNS cache too. It also uses DNS over HTTPS, depending on your settings and region.
To clear Firefox DNS cache:
- Open about:networking#dns.
- Click Clear DNS Cache, if shown.
- Restart Firefox.
Next, check DNS over HTTPS:
- Open Firefox Settings.
- Go to Privacy & Security.
- Scroll to DNS over HTTPS.
- Try turning it off.
- Or switch to another provider.
It drives me crazy that one browser can say “site broken” while another loads it in two seconds. But that is the clue. Browser-specific DNS settings matter.
Step 4: Flush DNS on your computer
If both Chrome and Firefox fail, clear DNS at the system level.
Windows:
ipconfig /flushdns
macOS:
sudo dscacheutil -flushcache
sudo killall -HUP mDNSResponder
Linux with systemd:
sudo resolvectl flush-caches
After that, restart the browser. Test again.
Step 5: Change DNS servers
Your ISP DNS can be slow or stale. Sometimes it just gives up. Very inspiring stuff.
Try these public DNS servers:
- Google: 8.8.8.8 and 8.8.4.4
- Cloudflare: 1.1.1.1 and 1.0.0.1
- Quad9: 9.9.9.9 and 149.112.112.112
You can set DNS on your device. Or set it on your router. Router setup helps every device on your Wi-Fi.
Image not found in postmeta
Step 6: Check the boring stuff
Yes, the boring stuff fixes many cases.
- Check spelling. One wrong letter can break everything.
- Disable VPN. Some VPN DNS servers are flaky.
- Disable proxy settings. Bad proxies cause weird failures.
- Restart the router. Wait 30 seconds before turning it on.
- Check the hosts file. A bad entry can block a domain.
- Try another network. Use a hotspot for a quick test.
Also check if the domain has expired. This happens more than people admit. A business forgets renewal. The site vanishes. Everyone blames Chrome.
A simple user case
Mia runs a small online store. One morning, Chrome shows Net::ERR_NAME_NOT_RESOLVED for her admin page. Panic begins. Coffee is involved.
She opens the same page in Firefox. It works. That tells her the site is alive. The domain is fine. Her Wi-Fi is fine.
She clears Chrome’s host cache. No luck. Then she turns off Chrome Secure DNS. Boom. The page loads after about five seconds.
The cause was a DNS provider delay. Not the website. Not the laptop. Not evil spirits.
So, Chrome or Firefox?
Use both. Chrome gives sharper error codes. Firefox gives a clean comparison. Together, they turn a vague DNS mess into a short checklist.
If Chrome says Net::ERR_NAME_NOT_RESOLVED and Firefox works, fix Chrome first. Clear Chrome DNS. Check Secure DNS. Flush sockets.
If both browsers fail, move wider. Flush system DNS. Change DNS servers. Restart the router. Test on mobile data.
The best fix is not guessing. Compare browsers first. Then clear the right cache. Then change DNS only if needed. That saves time, clicks, and a tiny piece of your sanity.