Start by testing the same site in both Chrome and Firefox before changing DNS settings. If Chrome shows ERR_NAME_NOT_RESOLVED while Firefox opens the site, the issue is likely browser cache, secure DNS, or an extension. If both browsers fail, focus on your network, DNS provider, router, or operating system.
TLDR: Chrome usually exposes DNS failures more clearly with ERR_NAME_NOT_RESOLVED, while Firefox may show a softer message such as “Hmm. We’re having trouble finding that site.” In a small office case, 7 out of 20 users could not load an internal dashboard in Chrome, but Firefox worked because Chrome had cached a bad DNS response. Clearing Chrome’s host cache and disabling Secure DNS fixed the issue in under 5 minutes. If both browsers fail, switch DNS to 1.1.1.1 or 8.8.8.8 and flush the system DNS cache.
What ERR_NAME_NOT_RESOLVED means
ERR_NAME_NOT_RESOLVED means the browser could not turn a domain name into an IP address. For example, it could not translate example.com into a server address like 93.184.216.34. Without that lookup, the browser has nowhere to send the request.
This is a DNS resolution error. It can come from the browser, the operating system, the router, the DNS resolver, or the domain itself. That is why switching browsers is a useful first test. It separates a Chrome problem from a wider DNS problem.
Chrome vs Firefox: which is better for fixing DNS errors?
Chrome is better for identifying the exact DNS error. Its error message is direct, searchable, and consistent. When Chrome says ERR_NAME_NOT_RESOLVED, you know the name lookup failed.
Firefox is better as a control test. It may not show the same technical code, but it helps confirm whether the problem is browser specific. If Firefox loads the site, Chrome is probably holding a bad cache entry or using a DNS setting that Firefox is not using.
Honestly, it feels like Chrome can be too “sticky” with DNS failures. A site may recover at the DNS level, but Chrome still refuses it for another minute or two because of cached data. That delay is small, but when a client is waiting on a login page, it feels much longer.
Common causes in Chrome
- Chrome DNS cache: Chrome keeps its own host cache, separate from the system cache.
- Secure DNS: Chrome may use DNS over HTTPS with a provider that cannot resolve the domain.
- Extensions: VPN, ad blocking, privacy, and security extensions can block lookups.
- Proxy settings: A bad proxy can prevent normal DNS resolution.
- Corrupted browser profile: Rare, but it happens after sync conflicts or crashes.
Common causes in Firefox
- DNS over HTTPS: Firefox can route DNS through its own provider, often Cloudflare, depending on settings and region.
- Stricter privacy settings: Enhanced Tracking Protection can break some poorly configured sites.
- Add ons: Security add ons may block domains before DNS completes.
- Cached failures: Firefox can cache failed lookups too, though it is often less obvious.
Fast test: compare both browsers
Open the same URL in Chrome and Firefox. Use the exact same address. Do not rely on search results or bookmarks. A typo such as mycompany.co instead of mycompany.com will waste time.
- Chrome fails, Firefox works: Fix Chrome first.
- Firefox fails, Chrome works: Check Firefox DNS over HTTPS, extensions, and privacy settings.
- Both fail: Check DNS provider, router, VPN, firewall, and domain status.
- Mobile data works, office Wi Fi fails: Your local network DNS is likely the issue.
How to fix ERR_NAME_NOT_RESOLVED in Chrome
- Clear Chrome host cache. Open chrome://net-internals/#dns and clear the host cache if available in your version.
- Restart Chrome. Close all Chrome windows, then reopen the browser.
- Turn off Secure DNS. Go to Settings > Privacy and security > Security. Disable Use secure DNS, or try another provider.
- Disable extensions. Open an Incognito window with extensions off. If the site works, re-enable extensions one by one.
- Clear browsing data. Remove cached images and files. Cookies are not usually the cause, but clearing them can help with login loops after DNS recovers.
How to fix the same DNS issue in Firefox
- Check DNS over HTTPS. Open Settings > Privacy & Security, then review DNS settings near the bottom of the page.
- Try “Default Protection.” Strict privacy mode can break some business portals and older sites.
- Restart without add ons. Use Troubleshoot Mode from the Help menu.
- Clear cache. Go to Settings > Privacy & Security > Cookies and Site Data.
- Create a fresh profile. Type about:profiles and test with a new profile if the issue keeps returning.
System level fixes when both browsers fail
If Chrome and Firefox both fail, stop blaming the browser. The DNS failure is probably outside the browser. Expect to waste time if you keep reinstalling Chrome at this point.
On Windows, open Command Prompt as administrator and run:
ipconfig /flushdnsThen restart the browser. If that fails, restart the router. Many home and small office routers keep stale DNS data longer than they should.
Next, change DNS servers. Good public options include:
- Cloudflare: 1.1.1.1 and 1.0.0.1
- Google Public DNS: 8.8.8.8 and 8.8.4.4
- Quad9: 9.9.9.9 and 149.112.112.112
For company networks, check internal DNS before changing anything. Internal tools often use private names that public DNS cannot resolve. If intranet.company.local fails only outside the VPN, that is expected behavior.
Chrome Secure DNS vs Firefox DNS over HTTPS
This is where many users get stuck. Chrome and Firefox can use encrypted DNS. That improves privacy, but it can also bypass your normal network resolver.
For example, your office DNS may know where crm.internal lives. A public encrypted DNS provider will not. So Chrome or Firefox may fail even though the network is fine. This often happens after browser updates, VPN changes, or new security policies.
If an internal domain fails, test with Secure DNS or DNS over HTTPS turned off. If the site works after that, report it to IT. The fix may require browser policy settings, split DNS, or VPN DNS changes.
Which browser gives the cleaner troubleshooting path?
Chrome wins for clear error codes. The message ERR_NAME_NOT_RESOLVED points directly to DNS. That saves time during support calls and ticket triage.
Firefox wins for comparison testing. Its separate DNS behavior makes it useful when Chrome is acting stubborn. If Firefox works, you can avoid resetting the whole network.
The best approach is not choosing one browser forever. Use both as diagnostic tools. Chrome tells you what failed. Firefox helps prove where it failed.
Practical order of repair
- Test the site in Chrome and Firefox.
- Test another site, such as a major news site or search engine.
- Check for typos in the domain.
- Disable VPN or reconnect it.
- Clear browser DNS and cache.
- Turn off Secure DNS or DNS over HTTPS temporarily.
- Flush system DNS.
- Restart the router.
- Change DNS servers if the issue affects many sites.
- Check whether the domain has expired or changed DNS records.
Final verdict: For ERR_NAME_NOT_RESOLVED, Chrome is the better browser for spotting the DNS failure, but Firefox is just as useful for proving whether Chrome is the problem. If only one browser fails, fix browser cache, encrypted DNS, extensions, and profiles. If both fail, move quickly to system DNS, router settings, VPN rules, or the domain’s DNS records.