Skip to content
Glitchary
ERR_NAME_NOT_RESOLVED6 troubleshooting steps3 sources linked

ERR_NAME_NOT_RESOLVED: check the hostname and DNS result

Chrome could not resolve the requested hostname. Check the exact address and compare its availability before repairing the browser; a public site's owner can inspect the DNS response for that hostname.

By Glitchary · Updated · 2 min read

The short version

  1. 01Check the URL's exact hostname for spelling mistakes.
  2. 02Try another website to separate one hostname from general browsing failure.
  3. 03Compare the same hostname in another browser or permitted network.
  4. 04Use Google's shared Chrome connection procedure when the failure follows the browser.
  5. 05As the owner of a public hostname, inspect its DNS response and diagnostic details.
  6. 06Give persistent resolution failures to the DNS operator or network administrator with the exact hostname.

Raw message

ERR_NAME_NOT_RESOLVED

Likely causes

  • The hostname is incorrect or cannot currently be resolved.
  • The domain's DNS answer or the device's resolution path needs investigation.

Check the exact hostname first

Google associates this code with a hostname that does not exist or whose address has changed. Our first check is spelling, followed by another website and the same hostname in another browser or permitted network. Keep the hostname fixed so a different working address is not mistaken for a repair.

Google Chrome: hostname-resolution error meaning

Public-site owners: inspect the DNS response

Google Public DNS provides a lookup form at dns.google and a detailed response with possible diagnostic comments. For a public domain you manage, inspect the failing hostname and record type. Its troubleshooting distinguishes resolution, delegation and DNSSEC issues; the DNS operator needs to correct the identified branch.

Google Public DNS: inspect and troubleshoot DNS results

Use the shared browser route for a local failure

Use the linked Chrome connection procedure when other browsers can resolve the same public site. For a workplace hostname, ask the network administrator about the intended internal resolution path. Our recommendation is to retain the exact hostname and successful comparison instead of changing DNS settings without establishing which resolver should answer.

Google Chrome: shared connection troubleshooting

Sources and review notes

Checked on . Based on Google's Chrome code meaning, shared connection guide and Public DNS troubleshooting. Scope comparisons and internal-network escalation are editorial guidance. Public DNS testing applies to public hostnames; a failed lookup does not identify one universal DNS-setting repair. Glitchary is independent of Google.

Tags

chromebrowsererr-name-not-resolveddnshostnameresolutiondomain