Server IP address could not be found

How to Fix “Server IP address could not be found”

DNS Error 📄 Chrome, Edge, Brave
⚡ Quick answer

This error means Chrome tried to look up the IP address for the website you visited but the DNS lookup failed. Your DNS server could not translate the domain name into an IP address.

First, check if your internet is working and what your current IP address is:

🔍 Check My IP Address →

What Causes the “Server IP address could not be found” Error?

Every website has an IP address. When you type a domain name, your browser asks a DNS server to look up the IP address — a process called DNS resolution. "Server IP address could not be found" means that lookup failed. This is essentially the same underlying problem as DNS_PROBE_FINISHED_NXDOMAIN but shown in a slightly different context. Causes include: your DNS server is down or unreachable, the domain genuinely does not exist, you have no internet connection, your hosts file has a conflicting entry, or your ISP is blocking the domain.

How to Fix It — 5 Methods

1 Check your internet connection

The most basic check — make sure you are actually connected to the internet.

  1. Try loading a different website (e.g. google.com)
  2. Check your Wi-Fi or ethernet connection indicator
  3. Try on another device on the same network
  4. Visit tools.examineip.com — if your IP loads, your internet is working
2 Flush DNS cache and renew IP

Clear your DNS cache and get a fresh IP from your router.

Windows:

  1. Press Win + R → type cmd → press Enter
  2. Run these commands one by one:
    ipconfig /flushdns
    ipconfig /release
    ipconfig /renew
    netsh winsock reset
  3. Restart your computer

Mac:

  1. Open Terminal
  2. Run: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
3 Switch to Google or Cloudflare DNS

Your ISP's DNS may be the problem. Switch to a public DNS server.

  1. Open your network adapter settings
  2. Set DNS to 8.8.8.8 (Google primary) and 1.1.1.1 (Cloudflare)
  3. Save and restart your browser

Alternatively, in Chrome go to Settings → Privacy and security → Security → Use secure DNS → choose Google or Cloudflare.

4 Check your hosts file

Your hosts file can override DNS and redirect domains to wrong IPs. Malware sometimes modifies this file.

Windows:

  1. Open Notepad as Administrator
  2. Open the file: C:WindowsSystem32driversetchosts
  3. Look for any lines mentioning the domain you are trying to visit
  4. Delete any suspicious entries and save

Mac:

  1. Open Terminal
  2. Run: sudo nano /etc/hosts
  3. Remove any suspicious entries for your domain
5 Use a VPN if your ISP is blocking the domain

If the site works on mobile data but not your home broadband, your ISP is likely blocking it. A VPN bypasses this.

  1. Connect to PureVPN or IPVanish
  2. Choose a server in a different country
  3. Try loading the site again
🔒
Some errors are caused by ISP blocks or network restrictions
A VPN bypasses them instantly by routing through a different server.

Fixed it? Visit tools.examineip.com to confirm your IP address and connection are working correctly.

Frequently Asked Questions

Is "server IP address could not be found" the same as DNS_PROBE_FINISHED_NXDOMAIN?
Yes, they are the same underlying problem shown in slightly different contexts. Both mean Chrome could not get an IP address for the domain from the DNS server. The same fixes apply to both.
Can a VPN fix "server IP address could not be found"?
Yes, if the cause is your ISP blocking the domain. A VPN uses its own DNS server and routes traffic through a different network, bypassing your ISP's DNS block entirely.
Does this error mean the website is offline?
Not necessarily. The site might be perfectly fine — it just means your browser cannot find its IP address. Try visiting downforeveryoneorjustme.com to check if the site is globally down.

Learn More About IP Addresses & Privacy

Other Internet Errors Explained

← Back to the complete guide: Internet Errors Hub

Last updated: March 29, 2026 • Report an error

Scroll to Top