How to Fix Error Code 105 ERR_NAME_NOT

DNS lookup failures prevent Chrome from accessing websites, resulting in the error message: ERR_NAME_NOT_RESOLVED or Error Code 105. This issue arises when Chrome cannot convert a domain name into an IP address, halting the connection process. The most common causes include DNS misconfiguration, outdated cached data, firewall restrictions, or temporary network problems. Addressing these root causes restores normal browsing and site accessibility.

Flush the DNS Cache on Windows 11

DNS cache stores mappings of domain names to IP addresses for quicker access. However, if this cache contains outdated or incorrect records, Chrome will fail to resolve the domain, displaying the error. Flushing the DNS cache clears these records and forces the system to request fresh information from DNS servers.

Press Windows + r to open the Run dialog, type cmd, then press Enter to launch the Command Prompt.

In the Command Prompt window, enter:

ipconfig /flushdns

After running the command, you should see a confirmation message stating that the DNS resolver cache was successfully flushed. This forces the system to update its DNS records the next time you attempt to visit a website.

Clear Chrome’s Host Cache and Browser Data

Chrome maintains its own DNS cache, separate from the operating system. Outdated entries here can also trigger DNS resolution errors. Clearing this cache, along with browser cookies and site data, removes stale information that may block website access.

Open Chrome and type chrome://net-internals/#dns into the address bar. Press Enter.

Click the Clear host cache button on the page. This removes all DNS records stored by Chrome.

To clear browser data, click the three-dot menu in the top-right corner, select Settings, then go to Privacy and security > Clear browsing data. In the popup, select All time for the time range, check all boxes (including Cookies and Cached images), and click Clear data. This removes cookies and cached files that could interfere with DNS resolution.

Disable Chrome’s Page Preloading Feature

Chrome’s preloading feature attempts to speed up browsing by prefetching resources and DNS information for predicted sites. If the cached DNS data becomes outdated, this can cause the ERR_NAME_NOT_RESOLVED error. Disabling preloading ensures Chrome fetches fresh DNS data for each request.

In Chrome, open Settings from the three-dot menu.

Navigate to Privacy and security > Cookies and other site data.

Scroll to find Preload pages for faster browsing and searching and toggle it off. This prevents Chrome from storing potentially outdated DNS information for future visits.

Restart Your Router and Test the Internet Connection

Network devices like routers can occasionally experience issues that disrupt DNS queries. Restarting the router refreshes its internal state and often resolves temporary connectivity problems.

Unplug your router’s power cable and wait at least 30 seconds to ensure a full reset.

Plug the router back in and wait for all status lights to indicate a stable connection (usually when the Internet/DSL light turns green).

Try accessing the problematic website again in Chrome. If the error persists, test the website using a different device or network connection (such as a mobile hotspot) to determine if the issue is specific to your original network.

Change DNS Server Addresses

Sometimes, the DNS servers provided by your ISP may be slow, unresponsive, or misconfigured. Switching to a public DNS service like Google DNS or Cloudflare DNS can resolve lookup failures and speed up domain resolution.

Open the Control Panel in Windows 11 and go to Network and Internet > Network and Sharing Center.

Click Change adapter settings on the left. Right-click your active network connection and select Properties.

Double-click Internet Protocol Version 4 (TCP/IPv4) or Internet Protocol Version 6 (TCP/IPv6) as appropriate.

Select Use the following DNS server addresses and enter one of the following:

Google DNS (IPv4): 8.8.8.8 and 8.8.4.4.
Cloudflare DNS (IPv4): 1.1.1.1 and 1.0.0.1.

Click OK to save your changes. Reconnect to the internet and test Chrome again.

Reset Windows Firewall Settings

Firewall or security software can block DNS requests or Chrome’s network access, causing DNS resolution errors. Resetting firewall settings restores default rules and removes unintended blocks.

Open Settings in Windows 11 and select Privacy & security > Windows Security.

Click Firewall & network protection, then scroll down and select Restore firewalls to default.

Confirm the reset by clicking Restore defaults. After the firewall resets, try accessing the website again in Chrome.

If you use third-party antivirus or firewall software, temporarily disable it and check if the error resolves. If so, add Chrome as an allowed application or adjust the firewall rules accordingly.

Disable DNSSEC for Your Domain (Website Owners Only)

DNSSEC (Domain Name System Security Extensions) adds cryptographic protection to DNS records. However, if DNSSEC is misconfigured or your domain recently changed hosts, DNS propagation issues can cause ERR_NAME_NOT_RESOLVED errors for all visitors. Disabling DNSSEC can restore normal resolution if this is the cause.

Use a WHOIS lookup tool to check if DNSSEC is enabled for your domain. Look for a “signed” status in the DNSSEC field.

If enabled, log in to your domain registrar or hosting provider dashboard. Locate the DNS or DNSSEC management section.

Remove or disable any DNSSEC records. Save your changes and wait for DNS propagation (which can take several hours).

After disabling DNSSEC, test your website in Chrome to confirm that the error no longer appears.

Additional Solutions and Maintenance Tips

Other factors, such as incorrect proxy settings, browser extensions, or malware, can also cause DNS resolution problems. Ensure proxy settings are correct (or disabled if not needed) in Chrome’s system settings. Temporarily disable suspicious extensions or run a malware scan with trusted security software if problems persist. Periodically clearing browser and DNS caches, as well as keeping your system and browser updated, minimizes the chance of future DNS errors.

Restoring DNS functionality in Chrome often comes down to clearing outdated cache, configuring reliable DNS servers, and ensuring network and firewall settings are correct. These targeted steps resolve most instances of error code 105 and ERR_NAME_NOT_RESOLVED, so you can get back to uninterrupted browsing.