Chrome ERR_NAME_NOT_RESOLVED
About Chrome ERR_NAME_NOT_RESOLVED
Chrome ERR_NAME_NOT_RESOLVED means the DNS lookup for the website domain name failed. This guide covers everything you need to know about this topic, including common causes, step-by-step solutions, and answers to frequently asked questions.
Here are the key things to understand: Chrome cannot convert the domain name to an IP address. DNS server is not responding or domain does not exist. Can affect specific domains or all websites. Common with mistyped URLs. Understanding these fundamentals will help you diagnose and resolve this issue more effectively.
The most common reasons this occurs include: Domain name misspelled in the URL. DNS server is down or unreachable. Domain has expired and been deregistered. DNS cache has stale or incorrect entry. Identifying the root cause is the first step toward finding the right solution.
To resolve this, follow these recommended steps: Check the URL for typos in the domain name. Flush DNS cache: chrome://net-internals/#dns. Change DNS to Google (8.8.8.8) or Cloudflare (1.1.1.1). Try accessing the site using its IP address directly. If these steps do not resolve the issue, consider consulting additional resources or a qualified professional.
This article is part of our Browser Errors collection on Error Codes Wiki. We provide comprehensive, up-to-date information to help you find solutions quickly.
Quick Answer
Does this mean the website does not exist?
Not necessarily — DNS may be temporarily down. Check the URL for typos first.
Overview
Chrome ERR_NAME_NOT_RESOLVED means the DNS lookup for the website domain name failed.
Key Details
- Chrome cannot convert the domain name to an IP address
- DNS server is not responding or domain does not exist
- Can affect specific domains or all websites
- Common with mistyped URLs
Common Causes
- Domain name misspelled in the URL
- DNS server is down or unreachable
- Domain has expired and been deregistered
- DNS cache has stale or incorrect entry
Steps
- 1Check the URL for typos in the domain name
- 2Flush DNS cache: chrome://net-internals/#dns
- 3Change DNS to Google (8.8.8.8) or Cloudflare (1.1.1.1)
- 4Try accessing the site using its IP address directly