ERR_NAME_NOT_RESOLVED in Chrome

• Estimated time: 3 min
• Easy
• Low risk

Start with the domain, not a cache wipe.

1. Check the address for typing mistakes. Use a known bookmark for the official address if available, and try another site.

2. If only an internal work name fails, confirm the required network or VPN with IT. Do not query it through public resolvers or change DNS to bypass that configuration.

• Estimated time: 5 min
• Easy

The query does not change network configuration.

1. Command PromptCopy

   nslookup example.com.

   Replace example.com. with the affected public hostname, ending in a dot and without https:// or a path. This uses the default DNS server and needs no administrator rights.

2. An address response shows that this query resolved. Nonexistent domain means that resolver did not find the name; timed out means it did not answer in time. Neither result alone identifies who must fix the problem.

3. Chrome may use a different resolution path, such as Secure DNS. If nslookup works but Chrome fails, report that difference before changing DNS.

• Estimated time: 4 min
• Easy
• Low risk

Keep specific comparisons for the site or network administrator.

1. Try the address in another browser on the same computer. If the failure stays in Chrome, update it and compare an Incognito window.

2. If the same public name also fails on other devices, give the name and DNS result to the site or network operator. Do not manually substitute a site IP address: it is not a safe replacement for its name.