ERR_NAME_NOT_RESOLVED means Chrome could not find an IP address for the domain you typed. The lookup failed before any connection was attempted. It can be a local DNS problem on your device or router, or a real problem with the domain's DNS – a missing record, wrong nameservers or an expired registration.
Before you start
- Check other sites load. If none do, your internet connection or resolver is down.
- Test the domain on mobile data to separate local from global problems.
Fix it on your device
- Check the spelling and remove odd characters.
- Flush DNS: Windows
ipconfig /flushdns; macOSsudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. See flush DNS cache. - Clear Chrome's host cache at
chrome://net-internals/#dns. - Check Chrome's secure DNS under Settings → Privacy and security → Security → Use secure DNS. Switch provider or turn it off to test.
- Change your DNS resolver to 1.1.1.1 or 8.8.8.8 in network settings.
- Check the hosts file for wrong entries, and restart the router.
Fix it as the domain owner
- Check the domain status with our WHOIS checker. Renew if expired, and complete any registrant email verification.
- Check nameservers at the registrar point to where your zone is hosted.
- Check the records exist:
dig example.com +shortanddig www.example.com +shortshould return your server IP. Add missing A or CNAME records in cPanel → Domains → Zone Editor. - Check for SERVFAIL: a DNSSEC problem also shows as this browser error. See DNS SERVFAIL errors.
Tip: If only www fails, the www record is missing. Add a CNAME for www pointing to the root domain.
FAQ
Is ERR_NAME_NOT_RESOLVED the same as NXDOMAIN?
Closely related; Chrome shows DNS_PROBE_FINISHED_NXDOMAIN when DNS explicitly says the name does not exist.
Why does the site work on Wi-Fi but not mobile data?
The networks use different resolvers, and one has an outdated or failed answer.
How long after registering a domain will it resolve?
Usually within an hour, sometimes up to 24–48 hours.