Fix Server DNS Address Could Not Be Found in Chrome

When Chrome shows “Server DNS address could not be found,” it means the browser couldn’t translate the website’s name into an IP address, so it couldn’t connect. The fix usually involves checking your internet connection, clearing the DNS cache, or switching to a public DNS server like Google’s (8.8.8.8). Below are the most effective steps to resolve this error, along with explanations of why each works.

What Causes This Error?

The Domain Name System (DNS) acts like the internet’s phonebook. When you type a URL, your device asks a DNS server to return the correct IP address. If that request fails, Chrome shows “Server DNS address could not be found.” Common triggers include:

• Your internet service provider’s DNS server is temporarily down or slow.
• Your router or device has a corrupted DNS cache.
• Your firewall or antivirus is blocking DNS requests.
• The website itself is offline or the domain has expired.
• You’re connected to a network that requires login (like a hotel or airport Wi-Fi) but you haven’t signed in yet.

Sometimes the issue is specific to one device, while other times it affects all devices on the same network. Testing another device helps narrow down the cause.

Quick Fixes to Try First

1. Restart your router and modem. Unplug them for 30 seconds, then plug back in. This often clears temporary network glitches.
2. Check if other websites load. If only one site fails, the problem is likely with that site, not your connection.
3. Try a different browser. If the error appears only in Chrome, clear Chrome’s DNS cache (see below).
4. Disable VPN or proxy. VPNs and proxies can interfere with DNS resolution. Turn them off temporarily to test.
5. Run Windows Network Diagnostics (Windows) or Wireless Diagnostics (macOS). These tools can automatically detect and fix common issues.

If these don’t work, move on to the more targeted solutions below.

How to Clear DNS Cache on Windows, Mac, and Chrome

Your computer stores recent DNS lookups to speed up browsing. If that cache becomes corrupted, it can cause the error. Clearing it forces your device to ask fresh.

Windows:

1. Open Command Prompt as administrator (search “cmd,” right-click, “Run as administrator”).
2. Type ipconfig /flushdns and press Enter.
3. You should see “Successfully flushed the DNS Resolver Cache.”

macOS:

1. Open Terminal (Finder > Applications > Utilities > Terminal).
2. Run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder (for macOS Ventura and later). For older versions, just sudo killall -HUP mDNSResponder.
3. Enter your password when prompted.

Chrome-specific cache:

1. In Chrome’s address bar, type chrome://net-internals/#dns and press Enter.
2. Click “Clear host cache.”
3. Also visit chrome://net-internals/#sockets and click “Flush socket pools.”

After clearing, restart Chrome and try the site again.

Change Your DNS Server to a Public One

If your ISP’s DNS is unreliable, switching to a public DNS like Google (8.8.8.8 and 8.8.4.4) or Cloudflare (1.1.1.1) often resolves the error. These services are fast and have high uptime.

Windows:

1. Go to Control Panel > Network and Internet > Network and Sharing Center > Change adapter settings.
2. Right-click your active connection (Wi-Fi or Ethernet) and select Properties.
3. Select “Internet Protocol Version 4 (TCP/IPv4)” and click Properties.
4. Choose “Use the following DNS server addresses” and enter:
• Preferred: 8.8.8.8
• Alternate: 8.8.4.4
5. Click OK and restart your browser.

macOS:

1. Go to System Settings > Network.
2. Select your connection, click Details, then DNS.
3. Click the plus sign and add 8.8.8.8 and 8.8.4.4.
4. Click OK and restart.

You can also change DNS on your router to fix it for all devices. Look for “DNS” settings in your router’s admin panel (usually at 192.168.1.1 or 192.168.0.1).

Disable Chrome’s Built-in DNS and Use System Settings

Chrome has a feature called “Use secure DNS” that sends DNS requests over HTTPS. Sometimes this causes conflicts. To disable it:

1. Open Chrome Settings (three dots > Settings).
2. Go to Privacy and security > Security.
3. Scroll to “Use secure DNS” and toggle it off.
4. Restart Chrome.

If you prefer to keep secure DNS, you can choose a specific provider from the dropdown instead of “With your current service provider.” Selecting Google or Cloudflare there may fix the issue.

Check Firewall and Antivirus Interference

Security software sometimes blocks DNS queries, especially after updates. Temporarily disable your firewall or antivirus to test. If the error disappears, add an exception for Chrome or your browser. On Windows, you can also check if the built-in Defender Firewall is blocking Chrome:

1. Go to Windows Security > Firewall & network protection.
2. Click “Allow an app through firewall.”
3. Find Chrome in the list and ensure both Private and Public boxes are checked.
4. If not, click “Change settings” and check them.

Be cautious: only disable security software temporarily and re-enable it immediately after testing.

Reset Network Settings (Advanced)

If nothing else works, resetting your network stack can clear deeper issues. This is a more drastic step and will forget Wi-Fi passwords.

Windows:

1. Open Command Prompt as administrator.
2. Run these commands one by one:
• netsh winsock reset
• netsh int ip reset
• ipconfig /release
• ipconfig /renew
• ipconfig /flushdns
3. Restart your computer.

macOS:

1. Go to System Settings > Network.
2. Select your connection, click Details, then TCP/IP.
3. Click “Renew DHCP Lease.”
4. If that doesn’t help, delete the Wi-Fi service and add it again (System Settings > Network > click “…” > Remove Service, then add it back).

Frequently Asked Questions

Why does the error happen only in Chrome and not in other browsers?

Chrome has its own DNS cache and secure DNS feature. If those are corrupted or misconfigured, Chrome fails while other browsers use the system DNS. Clearing Chrome’s cache or disabling secure DNS usually fixes it.

Does changing DNS affect my internet speed?

Yes, but usually positively. Public DNS servers like Google and Cloudflare are often faster than ISP servers, reducing the time it takes to load a website. However, the effect is small for most users.

Can this error be caused by malware?

Rarely, but malicious software can modify DNS settings or block connections. If you’ve tried all fixes and the error persists, run a full antivirus scan. Also check your system’s DNS settings (as shown above) to ensure they haven’t been changed to a suspicious server.

What if the error says “DNS_PROBE_FINISHED_NXDOMAIN”?

That’s a specific code meaning the domain doesn’t exist. Double-check the spelling, try a different domain like example.com, and if that works, the site is genuinely down or mistyped.

Will resetting my router fix this?

It can, if the router’s DNS cache is corrupted. A full reset (holding the reset button) restores factory settings, which clears all custom settings. Try a simple power cycle first; it’s less disruptive.

Is it safe to use public DNS servers?

Yes, major public DNS providers like Google and Cloudflare are reputable and widely used. They do log some query data, but they publish privacy policies. If privacy is a concern, you can use a DNS service that emphasizes no logging, like Quad9 or OpenDNS.

Related

• iPhone GPS Not Working? Fixes That Actually Help
• How to Create 3D Photos on Facebook
• Show the Developer Tab in Word: Step-by-Step