What Does ERR_NAME_NOT_RESOLVED Mean?
ERR_NAME_NOT_RESOLVED means your browser could not turn the website's domain name into an IP address, so it never reached the server. The cause is on your side (a typo, an old DNS cache, a broken DNS server, a VPN or Private DNS setting) or on the owner's side (wrong nameservers, a missing A record, or an expired domain).
- Visitor problem: the site opens on mobile data or another device, but not on your Wi-Fi or computer.
- Domain problem: the name fails for everyone, on every network. A DNS lookup shows no IP address for the domain.
- New or just-moved domain: the nameservers were changed in the last 24–48 hours and some networks still have the old answer.
Is It ERR_NAME_NOT_RESOLVED or a Different DNS Error?
Chrome shows several DNS and connection messages. They look alike, but the exact code under the message tells you where to look. If the name resolves but the page still does not load, read our ERR_CONNECTION_TIMED_OUT guide. For the related NXDOMAIN message, see how to fix DNS_PROBE_FINISHED_NXDOMAIN.
| Error | What it means | Where to look first |
|---|---|---|
| ERR_NAME_NOT_RESOLVED | The domain name could not be turned into an IP address | Spelling, DNS cache, DNS server, nameservers, A record |
| DNS_PROBE_FINISHED_NXDOMAIN | The DNS server answered that this domain or subdomain does not exist | Spelling, expired domain, missing record, nameservers |
| DNS_PROBE_FINISHED_NO_INTERNET | The device has no working internet connection | Wi-Fi, router, mobile data |
| ERR_CONNECTION_TIMED_OUT | The name was found, but the server never replied in time | Network, VPN, firewall, server load |
| ERR_CONNECTION_REFUSED | The server was reached but refused the connection | Web server stopped, wrong port, firewall rule |
How Do I Fix ERR_NAME_NOT_RESOLVED as a Visitor?
Try these steps in order. Test the website after each one.
1. Check the address
Look for a typo, a missing letter or the wrong ending, for example .com instead of .com.pk or .pk. Type the address yourself instead of using an old bookmark or a link from a message.
2. Try another network or device
Switch from Wi-Fi to mobile data, or open the site on another phone. If it works there, the problem is the DNS on your network or device, not the website.
3. Clear the DNS cache
Windows: open Command Prompt and run ipconfig /flushdns. macOS: open Terminal and run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. Chrome keeps its own cache: open chrome://net-internals/#dns, click Clear host cache, then restart the browser.
4. Change your DNS server
Your ISP's DNS server can be slow or down. Set a public DNS server such as Cloudflare (1.1.1.1 and 1.0.0.1) or Google (8.8.8.8 and 8.8.4.4) in your network adapter or router settings, then test again.
5. Check Private DNS on Android
On Android, open Settings and search for Private DNS (the menu names differ by phone). If a custom hostname is set and that DNS server is not working, many sites fail with this error. Choose Automatic, or turn it off, and test again.
6. Turn off VPN, proxy and DNS-filtering apps
VPNs, proxies, ad blockers and some antivirus apps change how DNS works. Turn them off one at a time. On Windows, also open C:\Windows\System32\drivers\etc\hosts and remove any line for the domain you cannot open.
How Do I Fix ERR_NAME_NOT_RESOLVED on My Own Website?
If the site fails for everyone on every network, the problem is in the domain or its DNS. Check these in order.
1. Confirm the domain has not expired
Check the domain in your registrar account or a WHOIS lookup. An expired or suspended domain stops resolving for everyone. Renew it first, then give DNS some time to come back.
2. Check the nameservers
The nameservers set at your registrar must point to the DNS host that holds your records. For cPanel hosting, these are usually your hosting provider's nameservers. A typo in one nameserver, or nameservers that still point to an old host, is the most common owner-side cause. For .pk domains, nameservers are changed through PKNIC; see our .pk nameserver guide.
3. Check the A records for @ and www
In cPanel Zone Editor (or your DNS provider's panel), the root domain (@) needs an A record with your server's IP address, and www needs an A record or a CNAME that points to the root domain. If only one exists, example.com may open while www.example.com fails, or the other way round. Our DNS records guide explains each record type.
4. Wait for propagation after a change
After a nameserver change, some networks can keep the old answer for up to 24–48 hours. Record changes inside the same DNS zone usually update sooner, depending on the record's TTL. A global DNS checker (such as whatsmydns.net) shows which locations already see the new IP address.
5. Check subdomains and DNSSEC
A subdomain such as shop.example.com needs its own record. If DNSSEC is turned on at the registrar but the DNS zone has moved to a new host, the old DS record can make lookups fail. Remove the DS record or update it with the new DNS host's details.
6. Test the domain with nslookup
Run nslookup example.com 8.8.8.8 and nslookup example.com 1.1.1.1. If both return an IP address, DNS works and the problem is limited to some networks or devices. If they return "Non-existent domain" or no answer, fix the nameservers or records.
How Long Does It Take for a New Domain to Resolve?
A new domain usually starts resolving soon after its nameservers are set, but some ISPs keep an old "does not exist" answer in their cache for a while. Nameserver changes can take up to 24–48 hours to reach every network. During that time the site may open on mobile data but fail on home Wi-Fi, or open for you but fail for a customer. This is normal. If the site still fails everywhere after 48 hours, check the nameservers and A records again.
When Should I Contact Support?
Contact your domain registrar or hosting support when the domain fails on every network, when the nameservers look correct but nslookup returns no IP address, or when you are not sure which nameservers to use. Send the domain name, the nameservers set at the registrar, the time the error started and a screenshot of the error. At Alif Host, sales and general support are available 24/7 on WhatsApp (+92 313 2946143), and the technical team works from 11 AM to 8 PM PKT. If you need a new domain, you can search and register .com and .pk domains in PKR.


