net::ERR_NAME_NOT_RESOLVED (This site can't be reached — server IP address could not be found)
DNS couldn’t resolve the hostname in the browser.
Exact message you may see
server IP address could not be found
Seen on:
JavaScript
Meaning
Typos, expired domains, missing DNS records, VPN-only internal hosts or DNS propagation delays after changes.
Common causes
- Typo in the domain
- DNS record missing or not propagated
- Internal hostname without VPN
- Local DNS/hosts file issues
⚡ Quick fix
- Check with nslookup/dig
- Fix DNS records at your provider
- Connect to VPN for internal hosts
- Flush DNS cache
Detailed fix by platform
Windows
ipconfig /flushdns
How to diagnose
- Domain — Exact hostname?
- DNS — Resolves from other networks?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in JavaScript
- TypeError TypeError: Cannot read properties of undefined (reading 'x')
- Failed to fetch TypeError: Failed to fetch / NetworkError when attempting to fetch resource
- module MIME type Failed to load module script: Expected a JavaScript module script but the server responded with a MIME type of "text/html"
Other ways to find it
Where this error sits
Origin: On your device. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Did this fix work for you?
Report a correction or suggest an improvement
Last updated 9 Oct 2026