Fix Server DNS Address Could Not Be Found in Chrome

This guide walks you through the most common fixes for the Chrome error “Server DNS Address Could Not Be Found.” This error means Chrome can’t translate the website’s name (like example.com) into a numeric IP address, so it can’t connect. You’ll learn how to clear Chrome’s DNS cache, switch to a public DNS server, and fix network settings that often cause this issue.

What You’ll Need

Access to your router’s admin page (usually via a web browser at an address like 192.168.1.1 or 192.168.0.1).
Administrator rights on your computer (to change network settings or run commands).
Your Wi-Fi password or Ethernet cable, in case you need to reconnect.

Step-by-Step

Check if the website is down for everyone. Open a different browser (like Firefox or Edge) and try the same URL. If it loads there, the issue is likely Chrome-specific. If it doesn’t load in any browser, the problem is your network or the site itself.
Clear Chrome’s DNS cache. In Chrome, type chrome://net-internals/#dns in the address bar and press Enter. Click the “Clear host cache” button. Then go to chrome://net-internals/#sockets and click “Flush socket pools.” Restart Chrome and try the site again.
Flush your computer’s DNS cache.
- Windows: Open Command Prompt as Administrator (press Windows key, type “cmd”, right-click and select “Run as administrator”). Type ipconfig /flushdns and press Enter.
- macOS: Open Terminal (Finder > Applications > Utilities > Terminal). Type sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder and press Enter. You may need to enter your password.
Restart your router and modem. Unplug both devices, wait 30 seconds, plug the modem back in, wait for it to fully boot, then plug the router back in. Once the lights stabilize, try the site again.
Change your DNS server to a public one. This is the most reliable fix. Using a public DNS like Google Public DNS (8.8.8.8 and 8.8.4.4) or Cloudflare (1.1.1.1 and 1.0.0.1) often resolves the error.
- Windows: Go to Control Panel > Network and Internet > Network and Sharing Center > Change adapter settings. Right-click your active connection (Wi-Fi or Ethernet) and select Properties. Select “Internet Protocol Version 4 (TCP/IPv4)” and click Properties. Choose “Use the following DNS server addresses” and enter 8.8.8.8 and 8.8.4.4. Click OK and restart your connection.
- macOS: Go to System Preferences (or System Settings) > Network. Select your active connection and click Advanced > DNS. Click the “+” and add 8.8.8.8, then add 8.8.4.4. Click OK and Apply.
- Router-level (applies to all devices): Log into your router’s admin page, find DNS settings (often under Internet/WAN settings), and change from “Automatic” to “Use the following DNS server” and enter 8.8.8.8 and 8.8.4.4. Save and reboot the router.
Disable Chrome’s built-in DNS resolver (if using a VPN or proxy). If you use a VPN or proxy, it may conflict. In Chrome, go to Settings > Privacy and security > Security. Scroll to “Use secure DNS” and turn it off. Try the site again. If it works, your VPN or proxy might be interfering.
Check your hosts file for bad entries. The hosts file can override DNS. On Windows it’s at C:\Windows\System32\drivers\etc\hosts. On macOS it’s at /etc/hosts. Open it with Notepad (Windows) or TextEdit (macOS) as administrator. Look for lines that contain the website you’re trying to reach. If you see any, add a # at the start of that line to comment it out, save, and restart your browser.
Reset Chrome flags. Type chrome://flags in the address bar, press Enter, and click “Reset all” at the top right. Restart Chrome. This clears experimental settings that might be causing issues.
Reinstall Chrome (last resort). If nothing else works, uninstall Chrome (make sure to back up bookmarks and passwords first), then download and install the latest version from the official site.

Common Mistakes

Typing the URL incorrectly – Double-check for typos, extra dots, or missing letters. Even a small mistake can cause a DNS lookup failure.
Flushing DNS without administrator rights – On Windows, if you don’t run Command Prompt as Administrator, the flush command may not work. On macOS, you need sudo.
Only clearing Chrome’s cache – The error often comes from your computer’s DNS cache, not Chrome’s. Always flush both.
Changing DNS on the wrong adapter – If you have both Wi-Fi and Ethernet, make sure you change DNS on the one you’re actually using. Changing the wrong one does nothing.
Forgetting to restart after changing DNS – Some changes only take effect after restarting your browser, computer, or router.

Tips

Use both DNS addresses – Always enter a primary and secondary DNS server. If one fails, the other is used automatically.
Try a different website – If only one site fails, it might be that specific site’s DNS record is temporarily broken. Check on a site like downforeveryoneorjustme.com to see if the site is down globally.
Keep your network drivers updated – Outdated network drivers can cause DNS issues. Check your device manufacturer’s website for updates.
Use Chrome’s Incognito mode – If the error only happens in normal mode, an extension might be the culprit. Try Incognito (Ctrl+Shift+N on Windows, Cmd+Shift+N on Mac). If it works there, disable extensions one by one.

Troubleshooting

If the error persists after changing DNS: Try using a different public DNS (e.g., Cloudflare 1.1.1.1 instead of Google). Sometimes one provider is blocked by your ISP.
If the error only happens on one device: The issue is likely that device’s settings. Try the steps on another device to confirm. If other devices work, focus on the problematic one.
If the error happens on all devices: The issue is your router or modem. Try restarting them again, and if that fails, log into the router and check for firmware updates.
If you use a VPN: Disconnect the VPN and try the site. If it works, the VPN’s DNS server is failing. Check the VPN’s settings for a DNS option, or contact their support.
If the error appears with “ERR_NAME_NOT_RESOLVED”: This is the same issue. Follow the same steps, but also check your firewall or antivirus software – they might be blocking DNS requests.
If you’ve tried everything and still get the error: It might be a problem with your ISP’s DNS infrastructure. Contact your ISP and ask if there are known DNS issues in your area.

Frequently Asked Questions

What does “Server DNS Address Could Not Be Found” mean?

It means Chrome couldn’t translate the website’s name into an IP address. Without that IP address, it can’t connect to the server.

Why does this error happen in Chrome but not in other browsers?

Chrome has its own DNS cache and sometimes its own DNS-over-HTTPS settings. If Chrome’s cache is corrupted or its secure DNS is misconfigured, it can fail while other browsers work.

Will changing my DNS server affect my internet speed?

Usually, it can slightly improve speed because public DNS servers like Google or Cloudflare are often faster than your ISP’s. However, the difference is usually negligible for everyday browsing.

Is it safe to use Google Public DNS?

Yes, it’s safe and widely used. Google Public DNS (8.8.8.8) is a reliable, free service. Your browsing data is still encrypted via HTTPS, and Google’s DNS logs are anonymized.

How do I reset Chrome to default settings without losing bookmarks?

Go to Chrome Settings > Advanced > Reset and clean up > Restore settings to their original defaults. This resets settings and disables extensions, but keeps your bookmarks, history, and passwords.

Can a firewall block DNS requests?

Yes, some firewalls or antivirus software may block DNS requests, especially if they have a “web protection” feature. Temporarily disable them to test, but re-enable after.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →