CheckWebsiteNow

Address lookup (DNS) errors

ERR_NAME_NOT_RESOLVED

The browser could not find the network address for this website name.

Quick answer

Every website name must be translated into a network address (an IP address) by DNS, the internet's address book. This error means that lookup failed. The name may be mistyped, the domain may have no working records, or your network's lookup service may be having trouble. Our check cannot tell whether a domain is registered.

When to wait: After a DNS change it can take time for the new records to spread; otherwise waiting rarely helps.

If you are visiting the website

  1. Check the address Look for typos in the web address, such as a missing letter or the wrong ending (.com instead of .de). If you got the link from an email or chat, copy it again in full.
  2. Try another network Switch from Wi-Fi to mobile data, or the other way round. If the site works there, your network or internet provider may be involved.
  3. Restart your router Turn your router off, wait about 30 seconds and turn it on again. This renews your connection and its address lookup.
  4. Clear your device's DNS memory Your device remembers recent name lookups (the DNS cache). A remembered failure can stick around even after the site is fixed, so clearing it forces a fresh lookup.
    Windows
    Open Start, type cmd and open Command Prompt. Run: ipconfig /flushdns.
    macOS
    Open Terminal (Applications > Utilities) and run: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. Enter your Mac password when asked; nothing shows while you type. Restarting the Mac has the same effect.
    Android
    There is no flush command. Turn Airplane mode on, wait ten seconds and turn it off again, or restart the phone.
    iPhone and iPad (iOS)
    There is no flush command. Turn Airplane Mode on in Control Center, wait ten seconds and turn it off again, or restart the iPhone.
  5. Clear Chrome's own DNS memory Chrome and Edge keep a second, separate list of recent lookups. Clearing it costs nothing and does not sign you out anywhere.
    Windows
    Type chrome://net-internals/#dns in the address bar, press Enter and click Clear host cache. In Edge use edge://net-internals/#dns.
    macOS
    Type chrome://net-internals/#dns in the address bar, press Enter and click Clear host cache.
  6. Check VPN, proxy and secure DNS A VPN, proxy or Chrome's secure DNS option can send lookups to a service that is not answering. Turn the VPN off once to test. Chrome shows its DNS service under More > Settings > Privacy and security > Security > Advanced > Use secure DNS.
  7. Try a public DNS resolver Your provider's DNS service (the address book your network uses) may be failing. Switching to a well-known public resolver tests this. Write down your current settings first; you can switch back at any time.
    Windows
    Start > Settings > Network & internet > Wi-Fi or Ethernet > your connection > DNS server assignment > Edit. Choose Manual, turn on IPv4, enter 1.1.1.1 and 1.0.0.1 (or 8.8.8.8 and 8.8.4.4) and click Save.
    macOS
    Apple menu > System Settings > Network > your connection > Details > DNS. Click + under DNS Servers, add 1.1.1.1 and 1.0.0.1 (or 8.8.8.8 and 8.8.4.4) and click OK.
    Android
    Settings > Network & internet > Private DNS > Private DNS provider hostname. Enter one.one.one.one or dns.google and tap Save. If you cannot find it, search Settings for Private DNS.
    iPhone and iPad (iOS)
    Settings > Wi-Fi > tap (i) next to your network > Configure DNS > Manual > Add Server. Add 1.1.1.1 and 1.0.0.1 and tap Save. This only changes that one Wi-Fi network.

If you run the website

  1. Test the name from outside Run dig example.com A +short and dig example.com AAAA +short, or on Windows nslookup example.com 1.1.1.1. If no address comes back, visitors cannot find your site either.
  2. Check DNS records Make sure the domain has A or AAAA records pointing to your server, and that every name you link to (www, shop and so on) has its own record.
  3. Check the nameservers Run dig example.com NS +short. The result must match the nameservers your DNS host told you to use; if the registrar still lists old ones, your records are never seen.
  4. Check domain renewal Log in to your registrar and confirm the domain has not expired.
  5. Plan for caching after changes Resolvers keep old answers for the record's TTL (time to live). Lower the TTL a day before planned moves so visitors pick up the new address sooner.

Is it the website or me?

Open the same address on your phone using mobile data. If it fails there too, the name itself is probably broken and only the owner can fix it. If it works there, your own network, router or DNS settings are the likely cause.

How it differs from DNS_PROBE_FINISHED_NXDOMAIN

ERR_NAME_NOT_RESOLVED only says the lookup failed. When Chrome shows DNS_PROBE_FINISHED_NXDOMAIN instead, it has also tested your DNS service and got a clear answer that the name does not exist. That points more strongly to a typo or a problem with the domain.

For developers: what happens technically

Before connecting, the browser asks a DNS resolver (a server that looks up names) for the A record (IPv4 address) or AAAA record (IPv6 address) of the host. If no usable address comes back, Chromium reports ERR_NAME_NOT_RESOLVED. No connection to the web server is attempted, so your server logs show nothing.

Common questions

Does this error mean the website is down?

Not necessarily. It means your device could not find the site's address. The server may be running fine, but nobody can reach it until the name lookup works again.

Is it safe to change my DNS server to 1.1.1.1 or 8.8.8.8?

Yes. These are well-known public resolvers run by Cloudflare and Google. Note your current settings first so you can switch back, and ask IT before changing a work or school device, because those networks sometimes need their own DNS.

Will flushing the DNS cache delete anything important?

No. It only removes remembered name lookups. Your files, passwords and browsing history stay untouched; the next visit simply looks the names up again.

Likely causes

  • Common A typo in the address. (Your side)
  • Common The domain's DNS records are missing, wrong or the domain expired. (Website side)
  • Sometimes Your network's DNS service has a problem. (Your side)

What to avoid

  • Do not install "DNS fixer" software from unknown sources.

Is the website down? Check it now

One measurement point. Results explain what we saw, not a worldwide verdict.

Sources

Last reviewed: