Fix Server DNS Address Could Not Be Found in Chrome

This guide walks you through fixing the “Server DNS address could not be found” error in Google Chrome. You’ll learn what causes it and how to resolve it step by step, from simple refreshes to changing your DNS settings. No special tools are needed—just a few minutes and access to your router or computer settings.

What You’ll Need

Access to your computer’s network settings (Windows or macOS)
Administrator rights on your computer (to change DNS or flush DNS cache)
Your router’s login credentials (usually printed on the router or in its manual)
An internet connection (even if it’s intermittent)

Step-by-Step

Refresh the page and check other sites. The error might be temporary. Press Ctrl+R (Windows) or Cmd+R (Mac) to reload. Try visiting a different website like example.com. If other sites work, the problem is likely with the specific site’s DNS, not your network.
Restart your router and modem. Unplug both devices, wait 30 seconds, then plug them back in. Wait for the lights to stabilize (about 2 minutes) and try the page again. This clears temporary network glitches.
Disable Chrome’s built-in DNS resolver. In Chrome’s address bar, type chrome://settings/security and press Enter. Scroll to “Use secure DNS” and toggle it off. Reload the page. If that fixes it, the issue is with Chrome’s DNS-over-HTTPS configuration.
Flush your DNS cache. Open Command Prompt (Windows) or Terminal (Mac). Type ipconfig /flushdns (Windows) or sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder (Mac) and press Enter. Restart Chrome and try again.
Change your DNS server to a public one. Go to your network adapter settings (Windows: Control Panel > Network and Sharing Center > Change adapter settings; Mac: System Preferences > Network > Advanced > DNS). Replace the current DNS servers with 8.8.8.8 and 8.8.4.4 (Google Public DNS) or 1.1.1.1 and 1.0.0.1 (Cloudflare). Save changes and reconnect.
Clear Chrome’s cache and cookies. Click the three-dot menu > More tools > Clear browsing data. Select “All time” and check “Cached images and files” and “Cookies and other site data.” Click “Clear data.” Restart Chrome.
Disable VPN or proxy settings. If you use a VPN, disconnect it temporarily. In Windows, go to Settings > Network & Internet > Proxy and ensure “Use a proxy server” is off. On Mac, check System Preferences > Network > Proxies. Try the site again.
Check your hosts file. Open the hosts file (Windows: C:\Windows\System32\drivers\etc\hosts; Mac/Linux: /etc/hosts) with Notepad or TextEdit. Look for any lines that mention the domain you’re trying to reach. If you see any, delete them and save the file. Restart Chrome.
Update your network drivers. On Windows, open Device Manager, find “Network adapters,” right-click your adapter, and select “Update driver.” On Mac, check for system updates in System Preferences > Software Update.
Restart Chrome in Incognito mode. Press Ctrl+Shift+N (Windows) or Cmd+Shift+N (Mac). If the site loads in Incognito, a Chrome extension is likely interfering. Disable extensions one by one (Menu > More tools > Extensions) to find the culprit.

Common Mistakes

Flushing DNS without admin rights: On Windows, you must run Command Prompt as Administrator. On Mac, sudo requires your password.
Typing the wrong DNS server address: A single typo like 8.8.8.8 vs 8.8.8.9 will fail. Double-check each number.
Forgetting to restart Chrome after changes: DNS settings are cached by the browser, so you must fully close and reopen Chrome.
Changing DNS on the wrong adapter: If you have both Wi-Fi and Ethernet, make sure you change the one you’re actively using.
Assuming the site is down: Sometimes the website itself has DNS issues. Check with a tool like downforeveryoneorjustme.com before messing with your system.

Tips

Use a reliable public DNS: Google (8.8.8.8) and Cloudflare (1.1.1.1) are fast and trustworthy. They often resolve sites faster than your ISP’s DNS.
Keep your router firmware updated: Log into your router’s admin page (usually at 192.168.1.1 or 192.168.0.1) and check for firmware updates. Outdated firmware can cause DNS problems.
Try a different browser: If the error only appears in Chrome, it’s a Chrome-specific issue. Testing in Firefox or Edge helps isolate the problem.
Use Chrome’s “Reset settings” as a last resort: Go to chrome://settings/reset and click “Restore settings to their original defaults.” This disables extensions and clears temporary data without deleting bookmarks.

Troubleshooting

If the error persists after trying all steps, consider these additional checks:

Test with another device: If your phone or tablet also fails to load the site, the problem is with your network or the site itself. If other devices work, it’s your computer’s configuration.
Check your firewall or antivirus: Some security software blocks DNS queries. Temporarily disable your firewall/antivirus and test. If the site loads, add Chrome to the allowed list.
Use a different network: Connect your computer to a mobile hotspot. If the site loads, your router or ISP is the issue. Contact your ISP if the problem persists on their network.
Run Windows Network Diagnostics: Right-click the network icon in the system tray and select “Troubleshoot problems.” This can automatically detect and fix DNS issues.
Check the site’s DNS status: Use an online DNS checker to see if the domain resolves globally. If it doesn’t, the site owner needs to fix their DNS records.

Frequently Asked Questions

What does “Server DNS address could not be found” mean?

It means Chrome couldn’t translate the website’s name (like example.com) into an IP address. This is usually due to a DNS server issue on your network, your device, or the website itself.

Will changing my DNS server speed up my internet?

Sometimes. A faster DNS server can reduce the time it takes to resolve domain names, but it won’t increase your download speed or bandwidth. It may make browsing feel snappier.

Is it safe to use Google’s public DNS (8.8.8.8)?

Yes, it’s safe and widely used. Google’s DNS is encrypted (DoH) when possible, and it doesn’t sell your browsing history. However, Google does log DNS queries for security, but the data is anonymized.

Why does the error only happen on one website?

Most likely the website’s DNS records are misconfigured or the site is temporarily down. You can’t fix that from your end; you just have to wait or contact the site owner.

Do I need to restart my computer after changing DNS settings?

No, but you should restart Chrome and possibly your network connection. Flushing DNS and restarting the browser is usually enough.

Can a VPN cause this error?

Yes. VPNs route your traffic through their own DNS servers, which may be slow or fail. Disconnecting the VPN or changing its DNS settings often resolves the issue.

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 →