ERR_NAME_NOT_RESOLVED: "server IP address could not be found"
Updated 17 November 2026
example.com's server IP address could not be found.
ERR_NAME_NOT_RESOLVED
What it means: your device tried to look up where the website lives and didn't get an answer.
It's very similar to DNS_PROBE_FINISHED_NXDOMAIN. Either the website's name is wrong or broken, or your device or network can't do the lookup right now. That's often caused by a VPN, Wi-Fi trouble or a setting, and it's usually quick to fix.
Don't worry: you haven't broken anything.
Step 1: Is it the website or you?
Type the website that won't load. We'll look it up from our server, away from your device and Wi-Fi.
The website's name really doesn't work right now. Check the spelling. If it's right, the site has a problem and you'll need to wait.
The website is fine, so your device or network can't find it. The fixes below usually solve it.
Step 2: Try these easy fixes first
Try them in order and reload the page after each one.
- Check the spelling Easy · 10 secondsLook for typos, and try with and without "www." at the start.
- Turn off your VPN Easy · 1 minuteThis error often appears while a VPN is switched on. Turn it off and try again.
- Try mobile data Easy · 1 minuteIf the site works on mobile data, the problem is your Wi-Fi network.
- Restart your Wi-Fi router Easy · 2 minutesUnplug it, count to 30, and plug it back in.
- Restart your device Easy · 2 minutesThis clears its saved list of website addresses.
Step 3: Still not working? Pick your device
Fix it on Windows
- Clear your PC's saved list of website addresses (flush the DNS cache). Click Start, type cmd, right-click Command Prompt, choose Run as administrator, and run:
ipconfig /flushdns
Advanced fixes for Windows
- Use a different address finder (change your DNS server): Settings › Network & internet › Wi-Fi (or Ethernet) › Hardware properties › DNS server assignment › Edit › Manual, turn on IPv4, and enter
1.1.1.1and1.0.0.1 - Reset your network in an administrator Command Prompt, then restart:
netsh winsock reset
Fix it on a Mac
- Turn Wi-Fi off and on from the Wi-Fi icon at the top right.
- Restart your Mac.
Advanced fixes for Mac
- Clear your Mac's saved website addresses (flush the DNS cache):
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder - Use a different address finder: System Settings › Network › Wi-Fi › Details › DNS, click +, and add
1.1.1.1
Fix it on Android
- Check "Private DNS". It's the most common cause on Android. Go to Settings › Network & internet › Private DNS (Samsung: Settings › Connections › More connection settings › Private DNS) and set it to Automatic.
- Turn Airplane mode on, wait 10 seconds, then turn it off.
Advanced fixes for Android
- Clear Chrome's cache in Settings › Apps › Chrome › Storage.
- Seeing it inside an app (as "net::ERR_NAME_NOT_RESOLVED")? Update the app, and clear its cache in Settings › Apps.
Fix it on iPhone and iPad
- Turn Airplane mode on and off.
- Turn off any VPN or DNS app in Settings › General › VPN & Device Management.
- Restart your iPhone or iPad.
Advanced fixes for iPhone and iPad
- Use a different address finder: Settings › Wi-Fi, tap (i) › Configure DNS › Manual, and add
1.1.1.1
Fix it on a Firestick or smart TV
- Unplug the Firestick or TV from the power for 30 seconds, then plug it back in. Restarting from the menu doesn't always clear the network.
- Restart your Wi-Fi router at the same time.
- Check the date and time on the device are correct. A wrong clock breaks lots of connections.
Advanced fixes for Firestick and TVs
- Set the DNS by hand, if your TV's network settings allow it: choose manual or advanced network setup and enter
1.1.1.1as the DNS. On a Firestick, the easiest way is to change the DNS on your router instead.
Why does this happen?
Before your device can open a website, it looks up the site's address in a kind of internet phone book called DNS. This error means that lookup failed. Common causes are:
- A typo, or a website whose domain has expired.
- A VPN sending your lookups somewhere that can't answer.
- Wi-Fi or router trouble, or your internet provider's address service having a bad day.
- Android's Private DNS, an ad blocker or parental controls filtering lookups.
Common questions
What does "server IP address could not be found" mean?
It means your device couldn't find the address of the website's server. The site's name may be wrong or broken, or your device or network couldn't do the lookup. Chrome shows it with the code ERR_NAME_NOT_RESOLVED.
What's the difference between ERR_NAME_NOT_RESOLVED and DNS_PROBE_FINISHED_NXDOMAIN?
They're very similar. NXDOMAIN means the lookup came back with "this name doesn't exist". ERR_NAME_NOT_RESOLVED means the lookup failed, which can also happen when your network didn't answer at all. The fixes are the same.
Why does it happen when I use a VPN?
Your VPN handles your website lookups. If its servers are slow, blocked or misconfigured, lookups fail. Switch to another VPN location, or turn the VPN off to test.
Why does it happen on my iPhone but not my computer?
Your iPhone may be using a VPN, a DNS app, or a different network from your computer. Turn off the VPN, toggle Airplane mode, and compare Wi-Fi with mobile data.
Is it your own website?
Check that your domain is still registered, that its nameservers point to your current DNS host, and that it has an A (or AAAA) record pointing to your server. Changes can take a few hours to reach everyone.
Related help
- DNS_PROBE_FINISHED_NXDOMAIN
- "This site can't be reached": every version explained
- "Safari can't open the page because the server can't be found"
Got another site that won't load?
Check any website