The “ERR_NAME_NOT_RESOLVED” on Chrome indicates a problem with domain name resolution (DNS) that is unable to translate a domain name into an IP address. This can be due to various reasons, ranging from DNS Configuration Issues to network connectivity problems. Corrupted browser cache or cookies, Firewall or Security Software blocking also cause err name not resolved on Chrome. This issue can be frustrating as it prevents loading webpages, sometimes affect multiple multiple websites while other times, it targets only specific websites. This article explores different solutions on How to fix NET::ERR_NAME_NOT_RESOLVED in Chrome.
Fix ERR_NAME_NOT_RESOLVED Chrome
The “NET::ERR_NAME_NOT_RESOLVED” error in Chrome means that the browser couldn’t find the address of the website you trying to visit. This happens because the DNS (Domain Name System) couldn’t translate the website’s name into the correct IP address.
DNS is responsible for resolving domains, and every domain on the internet has a name server, which makes it possible for the DNS to resolve Domain Names.
What causes the net err_name_not_resolved error?
There are plenty of reasons for this error, Unstable internet connection, problems with DNS configuration or DNS client service not running or corrupt browser cache data are common.
- The DNS server itself might be down, slow, or experiencing technical problems
- Your computer’s DNS settings might be misconfigured, preventing it from communicating effectively with DNS servers.
- Due to No internet connection, your browser won’t be able to reach the DNS server to perform the domain name resolution.
- Firewall or security settings on your computer can sometimes block the communication between your browser and the DNS server.
- Corrupted or outdated browser cache or cookies can interfere with the DNS resolution process.
Solutions for NET::ERR_NAME_NOT_RESOLVED on Windows 11
You need to ensure the internet connection is working, Clear browsing Data, and restart the DNS client service probably fixes the problem. Sometimes changing DNS server address help restore internet access and fix net err_name_not_resolved on Chrome.
Check Internet connection
A stable and functional internet connection is essential for proper DNS resolution. If your connection is weak or interrupted, it can lead to the “err name not resolved” error.
- First, make sure you have a stable internet connection to connect and access the web page you try to visit.
- Open a new tab in your browser and try accessing a different website to confirm that your internet connection is working.
Press the Windows key + R, and run the ping command ping google.com -t to check internet stability.
Restarting your router helps resolve potential network connection issues and refreshes the connection to your ISP’s DNS servers.
- Unplug your router for 30 seconds, then plug it back in. Wait for the internet light to turn green. Same time reboot your computer as well.
- Now try to access the website again.
If you are using a WiFi network, take your laptop closer to the wifi router and check if there is no more error while loading web pages.
Clear Browsing Data
Chrome keeps cache and cookies data to enhance the browsing experience. Accumulated or corrupted Cached data in your browser can sometimes cause net err name not resolved. Clearing browsing data removes potentially outdated or corrupted information.
- Type chrome://settings in the Chrome address bar and press enter key to open Chrome settings,
- Navigate to “Privacy and security” and select “Clear browsing data.”
- Choose “Cookies and other site data” and “Cached images and files,”
- Select the Time range all time then click “Clear data.”
Reload the webpage to check if the issue is resolved.
Clear Your DNS Cache (DNS Flush)
Flushing the DNS cache helps by clearing outdated or incorrect domain names and IP address information stored on your computer. This ensures that when you access a website, your computer fetches the most up-to-date information from DNS servers.
Flushing DNS can resolve issues where your browser can’t find the correct IP address for a website,
- Press Windows key + S, type cmd and select run as administrator
- This will open the command prompt with administrative privileges.
- Type the command ipconfig /flushdns and press enter
Restart your computer and try access the website again to check if err name not resolved solved.
Another reason for this problem is your proxy setting. I suggest you disable the proxy to see if it repairs the error you are encountering on Google Chrome.
- Press Windows + R, type inetcpl.cpl and click ok to open Internet Options.
- Then move to the Connections tab and then click on LAN settings.
- Here Check Automatically detect settings and keep other options unchecked.
- Click on OK and save the settings.
VPNs and firewalls can sometimes interfere with DNS resolution. Temporarily disabling them can help determine if they are causing the issue. Disable your VPN or firewall temporarily, then attempt to access the website.
Change DNS address to Google Public DNS
Switching to a different DNS server, such as Google DNS, can help if the default DNS server is experiencing problems. This can resolve DNS-related issues, including “ERR_NAME_NOT_RESOLVED,” by providing accurate and up-to-date IP address information for websites.
- Press Windows + R, type ncpa.cpl and hit the enter key.
- This will open the network connections window,
- Right-click on your active network connection and select “Properties.”
- Select “Internet Protocol Version 4 (TCP/IPv4)” and click “Properties.”
Choose “Use the following DNS server addresses” and enter the preferred and alternate DNS server addresses (e.g., 188.8.131.52 and 184.108.40.206 for Google DNS).
Also, Checkmark on Validate settings upon exit, and click ok to make save changes. Now open google chrome and check there no more NET::ERR_NAME_NOT_RESOLVED errors.
Reset Network configuration
Whenever you found a browser not loading web pages, Flushing and renewing DNS is a very good way to fix these types of errors. This is quite easy to perform and it is very effective to fix ERR_NAME_NOT_RESOLVED on the Chrome browser.
- Open the command prompt as administrator
- Once the command prompt window appears, type in the following commands one after another and hit Enter after each line.
netsh winsock reset
- After that type exit to close the command prompt and restart your computer. Then see if the error is fixed.
Flush Chrome DNS
Open a new tab in Chrome and enter the following in the address bar;
On the page that opens, click the “Clear host cache” button to flush the Chrome DNS cache.
Close the Chrome browser, Restart the PC and check on the next login check there is no more err_name_not_resolved problem.
Disable the prediction feature
Chrome’s prediction function promises to make browsing faster, But few users report that Disable the prediction feature helps them restore the internet on the Chrome browser.
Chrome’s preloading feature might interfere with DNS resolution. Disabling it can prevent conflicts and potential errors.
- First Open the Chrome browser on your computer
- Type chrome://settings in your address bar and hit go to access chrome settings
- Click on Privacy and Security from the sidebar. On the main page, click on the Cookies and other site data button to be redirected.
- Scroll down until you see the Preload pages for faster browsing and searching setting. Click on the toggle so that the feature is turned off (shows up grey).
Sometimes VPNs and firewalls might interfere with DNS resolution. Temporarily disabling them helps determine if they are responsible for the error.
Agin Malware infection can alter DNS settings and cause various internet-related problems, including DNS resolution errors. Perform full system scan with the latest updated antivirus or antimalware program to Remove malware can restore proper DNS functionality.
- How to Make Google Chrome Faster on Windows 10, 8.1 and 7
- Fix DNS probe finished nxdomain error on Google Chrome.
- Solved: Windows 10 start menu search not working after update
- Fix This app couldn’t be installed error 0x80073cf9 Windows 10
- Solved: Windows 10 Sandbox, no hypervisor was found (0xc0351000)