"Server IP address could not be found" means your browser asked DNS for a website's numeric IP address and got no usable answer, so it never started the connection. Chrome usually shows it as "[site]'s server IP address could not be found", often with the code DNS_PROBE_FINISHED_NXDOMAIN. Restarting the router, flushing the DNS cache, or switching to a public DNS server fixes most cases; on Android, also check the Private DNS setting. If you are still new to VPNs and networking basics, start with our complete VPN guide.

Key Takeaways

This is a DNS resolution problem: your browser cannot find the IP address for the site.

Use a simple troubleshooting order: check your connection first, clear browser and DNS caches next, then change DNS servers.

A stronger long-term fix: if DNS errors and hijacking happen often, use a stable privacy tool with encrypted DNS support.

What does "server IP address could not be found" mean?

If the DNS lookup fails at any point, the browser may show "Server IP address could not be found." The DNS server might not respond, the site may have moved, or your local device may be holding a broken record.

Why does this error happen?

In testing across multiple environments, the issue usually comes from five causes:

DNS server failure: the DNS server assigned by your ISP may be down or under maintenance［1］.
Target website problems: the site may be offline, under attack, or waiting for new DNS records to propagate.
Local configuration or cache errors: your operating system or browser may store stale or damaged DNS records.
Overactive security software: some antivirus tools and firewalls can mistakenly block DNS queries.
Proxy or VPN tool conflicts: unstable proxy nodes or leftover virtual network settings can break name resolution.

How to fix the error

Try these steps in order, from easiest to more advanced.

1. Check your connection and restart the router

Confirm that Wi-Fi is connected and that other devices can access the internet. Then unplug your modem or router, wait 30 seconds, and plug it back in. This forces the router to request fresh IP and DNS settings from your ISP.

2. Clear browser cache and cookies

Sometimes the browser is the only thing holding bad data. In Chrome:

Click the three-dot More menu in the top-right corner and choose Delete browsing data.
Select Cached images and files and Cookies and other site data.
Set the time range to All time.
Click Delete data, then restart the browser［2］.

3. Use incognito mode or another browser

Open the same site in a new incognito or private window. If it loads, a browser extension or old cache entry is probably the cause.

4. Flush DNS cache and reset network settings

Your operating system's DNS cache can become stale or corrupted.

On Windows:

Search for cmd, right-click Command Prompt, and choose Run as administrator.
Enter ipconfig /flushdns.
Enter netsh winsock reset.
Restart your computer［1］.

On macOS:

Open Terminal.
Enter sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder.
Type your administrator password and confirm.

5. Renew your IP address

Windows users can ask the system to get a fresh IP address. In Command Prompt, run:

Release the old IP: ipconfig /release
Request a new IP: ipconfig /renew

6. Change to a public DNS server

If your ISP's DNS keeps failing, switching to a public resolver is often one of the most effective fixes［3］.

Common free public DNS options:

Google DNS: 8.8.8.8 and 8.8.4.4
Cloudflare DNS: 1.1.1.1 and 1.0.0.1

On Windows 11, open Settings > Network & internet, then select Wi-Fi > Manage known networks and your network (or Ethernet). Next to the IP or DNS server assignment, select Edit, choose Manual, turn on IPv4, and type the addresses into Preferred DNS and Alternate DNS［4］.

7. Check proxy and network settings

If a third-party proxy tool crashes or exits badly, it may leave proxy settings behind at the system level.

Check proxy settings: search for "proxy settings" in Windows and turn off unnecessary manual proxy settings.

8. Temporarily disable antivirus or firewall software

Some web protection modules block DNS queries by mistake. Disable protection for five minutes and test again. If the site loads, add it to the firewall or antivirus allowlist.

9. Check the Windows DNS Client service

If you are on Windows, a stuck DNS Client service can break resolution across the system.

Press Win + R, type services.msc, and press Enter.
Find DNS Client and confirm its status is Running.
Current Windows versions usually grey out the restart option for this service, so restart the computer if it looks stuck.

10. Run the built-in network diagnostics tool

On Windows, open the Get Help app and run the Network and Internet troubleshooter［1］. On macOS, hold Option, click the Wi-Fi icon, and choose Open Wireless Diagnostics.

How do I fix "server IP address could not be found" on Android?

On an Android phone, the same error in Chrome often comes from the network you are on or from the phone's own DNS setting.

Switch networks: turn airplane mode on for 10 seconds, then try Wi-Fi and mobile data separately. If only one network fails, its DNS is the problem.
Check Private DNS: on Android 9 and later, open Settings > Network & internet > Private DNS (on some phones it sits under Advanced or a more connection settings menu). A mistyped or unreachable hostname makes every lookup fail, so choose Automatic or enter a valid provider hostname such as dns.google［5］.
Clear Chrome data: in Chrome, open Delete browsing data from the menu and clear cached files for the affected period.

Summary

When you see "server IP address could not be found," use this sequence:

Basic checks: restart the router, clear browser cache, and try incognito mode.
Deeper fixes: flush DNS cache, renew your IP, or switch to reliable public DNS such as 8.8.8.8 or 1.1.1.1.
Final cleanup: check proxy leftovers, disable overly aggressive security software, or run system diagnostics.
On Android: compare Wi-Fi with mobile data and reset a broken Private DNS hostname.

FAQ

Why does only one website show this error?

If most sites work, the target site may be down, its DNS records may not have propagated, or that specific content may be blocked by your current network.

Is changing DNS servers risky?

Usually no. A trusted public DNS resolver may be more stable and less prone to hijacking than a default local ISP resolver.

Can a network connection tool cause this error?

Yes. If a proxy or VPN client crashes without cleaning up proxy tables, routes, or DNS settings, name resolution can fail. A product with private DNS control lowers that risk.

Will flushing DNS cache delete my passwords or bookmarks?

No. DNS cache only stores temporary domain-to-IP records. It does not touch passwords, bookmarks, or personal files.

How do I fix this on an iPhone?

Turn airplane mode on for 10 seconds, then turn it off. If that fails, open Settings > Wi-Fi, tap the info button next to your network, and under Configure DNS switch to Manual to add a server such as 1.1.1.1.

Can malware cause this error?

Yes. Malware can change DNS settings, redirect traffic to malicious servers, or block certain domains. Run a full scan before checking DNS settings again.

Why does the error disappear on another Wi-Fi network?

That strongly suggests the original network's DNS configuration is the problem, not your device. The router may be forwarding DNS incorrectly, or the ISP resolver may be failing.

Disclaimer Some advanced troubleshooting steps in this article change system network settings. Make sure you understand each step before running commands, because incorrect changes may cause temporary or persistent connection issues. AethoVPN is not a repair for an invalid hostname or broken local DNS; compare resolver results and the site's status before changing the VPN route.

Sources

［1］ Microsoft Support: Fix Wi-Fi connection issues in Windows
［2］ Google Chrome Help: Clear cache & cookies
［3］ Cloudflare: What is 1.1.1.1?
［4］ Microsoft Support: Essential network settings and tasks in Windows
［5］ Google Public DNS: Get started

Sources checked 4 October 2026.

Related Articles:

Server IP Address Could Not Be Found