Troubleshoot Chrome ERR_NAME_NOT_RESOLVED

Affected products and symptoms

Product

Google Chrome

Versions and conditions

Chrome for computer

Error codes and identifiers

ERR_NAME_NOT_RESOLVED

Symptoms

• The site cannot be reached
• The host name cannot be found

Causes and conditions

The host may not exist, its IP address may have changed, the URL may be wrong, or DNS may be failing.

Before you start

• Record the complete URL, error code, and time
• Check whether a VPN or internal DNS is in use

Step-by-step instructions

1. 01

   Verify the URL

   #

   Check the domain spelling and navigate from the official home page rather than a link in email.

   Confirm that the error page says ERR_NAME_NOT_RESOLVED. Distinguish text entered as a search from a URL, and check a copied URL for extra spaces or missing characters.

   Select Advanced on the error page only to record the code. Select only the hostname in the address bar and check spelling and extra spaces. Do not move to a suspicious look-alike domain from search results.

2. 02

   Compare another site

   #

   Open another known site in the same Chrome session and determine whether only the target or all sites fail.

   A hostname used only inside a company may not resolve from an outside network. If only an internal site fails, do not infer that the network is healthy merely because public sites open; confirm the internal connection requirements.

3. 03

   Compare another device

   #

   Open the target URL on another device connected to the same Wi-Fi to distinguish a device problem from a network-wide problem.

   Record whether the same URL fails or opens on the other device. Change only one of device, network, and site at a time so the reproduction conditions given to an administrator are clear.

4. 04

   Renew the connection

   #

   Restart Chrome and the PC, then reconnect Wi-Fi. Reconnect a VPN only through the administrator-approved method.

   For home Wi-Fi, confirm the network in the taskbar list, disconnect once, and reconnect to the same network. Do not delete corporate VPN or proxy settings based on guesswork; ask the responsible person whether the site requires that connection.

   Official links for this step

   • Official Google Chrome troubleshooting ↗

     Check the official page for exact setting names, limitations, and updated decision paths.

5. 05

   Escalate the evidence

   #

   If only another network works, report it to the DNS administrator. If it fails on multiple networks, give the URL and time to the site operator.

   Include the target domain, occurrence time, Chrome version, and results from another site and device. Do not share a URL containing a password or authentication token unchanged; use the method specified by the site administrator.

Check the result

• The page opens at the correct URL
• You can explain the scope of the failure

If the problem continues

• For an internal site, ask the administrator about internal DNS requirements
• If other browsers also fail, defer resetting Chrome

Scope of this guide

Troubleshooting guide — A general diagnostic and recovery procedure based on official support; it does not indicate a current specific incident.

Frequently asked questions

Official sources and dates

• Get help with common error messages in Chrome ↗
• Fix connection and loading errors in Chrome ↗

Source publication or resolution date: Not specified. Sources checked: 2026-09-05. The check date is not the date the problem first occurred. Interface labels can vary between versions and display languages.

Related troubleshooting guides

• Isolate GPU-related Chrome crashes, freezes, or startup failures
• Troubleshoot Chrome ERR_CONNECTION_RESET
• Safely troubleshoot Chrome NET::ERR_CERT_DATE_INVALID
• Chrome: Review a Blocked Download Safely
• Identify the source of Chrome “Managed by your organization”
• Firefox crashes or displays text and page elements incorrectly

Get more from Google Chrome

• Separate work and personal profiles in Chrome