Ah, the dreaded ERR_NAME_NOT_RESOLVED – the bane of internet users everywhere. Imagine this: you’re happily browsing away, ready to dive into a new website or revisit an old favorite, when BAM! Your screen mocks you with those intimidating, all-caps words. But fear not, my friend, for beyond this cryptic error lies a realm of tech quirks and digital conundrums just waiting to be deciphered.understanding the topic

So, what’s causing this headache? Well, it could be a wonky DNS server, a mistyped URL, or even just a shoddy internet connection. Sometimes, it’s like your browser’s playing hard to get, blocked by firewalls or pesky network rules.

Understanding ERR_NAME_NOT_RESOLVED is like embarking on a quest for knowledge, delving deep into the heart of cyberspace where bytes and bits waltz in a delicate dance of communication. At its core, this error signals a breakdown in the very essence of internet navigation. When you punch in a web address, your browser has to translate that human-friendly domain name into a string of numbers that computers can understand. But when that translation fails, chaos reigns supreme, leaving you stranded in a whirlpool of digital confusion.

So, let’s see how to fix this error;

Solution #1: Clear Chrome’s Host Cache

Ever wondered what Chrome’s Host Cache, or DNS cache, actually does? Well, it’s like a little storage unit in Chrome’s brain where it keeps track of recent website addresses you’ve visited. You know when you type in something like “www.example.com” and magic happens, taking you to the right place on the internet? That’s the job of this cache—translating those human-friendly addresses into computer-friendly ones (IP addresses).

But sometimes, this cache can go a bit wonky, leading to those frustrating network errors. Luckily, we can give Chrome a little brain cleanse to fix it up.

Here’s how:

  1. Open up Google Chrome and head to the address bar.
  2. Type in: chrome://net-internals/#dns
  3. Hit Enter, and you’ll dive into Chrome’s secret network settings.
  4. Look for the button that says “Clear host cache” next to the Host resolver cache section.Clear Chrome’s Host Cache
  5. Click that button like you’re giving Chrome a little mental refresh.
  6. Once you’ve done that, Chrome will clear out its DNS cache, getting rid of any old or glitchy info. This should hopefully sort out any address-related hiccups and make your browsing smoother than ever.

Just remember to close and reopen Chrome to let the changes kick in properly.

Solution #2: Clear The Computer’s Saved DNS Cache

When you’re stuck dealing with persistent DNS problems like the dreaded “ERR_NAME_NOT_RESOLVED” error, it might be high time to give your computer’s DNS cache a good old clear-out. While we’ve already covered how to clean up Chrome’s Host Cache, it’s worth noting that your operating system also keeps its own stash of DNS info. Here’s how you can clear out the DNS cache on both Windows and macOS:

For Windows OS:

  1. Press the Windows Key + R to open up the Run dialog.
  2. Type “cmd” into the box and hit Enter to launch the Command Prompt.
  3. In the Command Prompt window, type “ipconfig /flushdns” (without the quotes) and hit Enter to flush out the DNS resolver cache.ipconfig /flushdns
  4. Once the command has done its thing, type “exit” and hit Enter to close the Command Prompt.

For macOS:

  1. Fire up the Terminal app on your Mac.
  2. Depending on your macOS version, use one of the following commands:
    • For Mac OS X El Capitan: sudo killall -HUP mDNSResponder
    • For Mac OS X Yosemite: sudo discoveryutil udnsflushcaches
    • For Mac OS X Mavericks: sudo killall -HUP mDNSResponder
    • For Mac OS X Mountain Lion: sudo killall -HUP mDNSResponder
    • For Mac OS X Lion: sudo killall -HUP mDNSResponder
    • For Mac OS X Snow Leopard: sudo dscacheutil -flushcache
  3. Type the appropriate command for your macOS version into Terminal and hit Enter to execute.
  4. You might have to enter your admin password to confirm the action.

Once the command has run successfully, your DNS cache will be squeaky clean.

By following these steps, you’ll be clearing out both Chrome’s Host Cache and your computer’s DNS cache, potentially solving all sorts of DNS-related woes and giving you a smoother browsing ride. And if you’re using an OS other than Windows or macOS, just hit up the search engine for tailored instructions.

Solution #3: Renewing New IP Address

Alright, so let’s talk about getting a fresh IP address. Imagine your device as a guest at a fancy party (the internet), and it needs a new name tag to fit in. Well, renewing your IP address is like getting that new name tag. It’s a process where your device asks the network’s fancy server (DHCP) for a new identity.

This whole thing can be a lifesaver when you’re facing issues like network errors. Sometimes, your current IP address might be causing problems, like clashing with someone else’s or just being outdated.

Now, if you’re on Windows:

  1. First off, open up the Command Prompt. You can find it in the depths of your Windows system.
  2. Then, type in ‘ipconfig /release’ and hit Enter. This lets go of your current IP address.
  3. After that, follow it up with ‘ipconfig /renew’ to grab a fresh one from the DHCP server.ipconfig /renew
  4. Once you’re done, close up that Command Prompt and give your computer a restart to seal the deal.

And for the Mac folks out there:

  1. Click on that cute little Apple logo in the top-left corner of your screen and select ‘System Preferences’.
  2. From there, dive into your Network settings.
  3. Find your active network connection and give it a click.
  4. Hit the ‘Advanced’ button like a pro.
  5. Then, up in the top menu, select ‘TCP/IP’.
  6. Now, you’re ready to hit that ‘Renew DHCP Lease’ button and snag a new IP address.'Renew DHCP Lease' in mac os
  7. Close up those settings, reboot your Mac, and you’re good to go.

And there you have it! Fresh IP, fresh start. Go forth and surf the web without a hitch.

Solution #4: Clear Browser Data

This frustrating error can sometimes be caused by a buildup of junk in your browser’s history and cache. Luckily, there’s a simple fix: clearing out this digital clutter can often get your browsing back on track.

To kick off this cleanup mission, just hit “Ctrl + H” on Windows or “⌘+Y” on Mac to bring up your browser’s history page. Once there, click on the “Clear browsing data” button at the top of the screen to start the purge. Make sure to tick both the “Cache” and “Cookies” checkboxes – they’re key storage spots for website data. Then, in the dropdown menu, go big with the “Select from the beginning of time” option to ensure a thorough sweep of all that accumulated digital gunk.

With those steps done, you’re ready to wave goodbye to the clutter slowing down your browser. After the clearing is finished, give your browser a refresh and try loading up those troublesome sites again. More often than not, this simple yet effective remedy will squash that pesky “ERR_NAME_NOT_RESOLVED” error and have you browsing smoothly once more.

Clear Browser Data

Solution #5: Change DNS IP To Google’s Public DNS

Switching to Google’s Public DNS can be a smart move to troubleshoot and fix problems like this network error. Google’s DNS is known for its strong and reliable infrastructure, often outperforming the default DNS servers provided by your Internet Service Provider (ISP). By making this switch, you can sidestep potential DNS issues caused by your ISP’s servers, leading to a smoother and faster internet connection.

For Windows:

  1. Start by opening the “Network and Sharing Center”. You can do this quickly by pressing the Windows key + R, typing ncpa.cpl, and hitting Enter.
  2. In the Network and Sharing Center, go to “Change adapter settings” on the left.
  3. Right-click on your active internet connection (like Local Area Network or Wireless Area Network) and select Properties.
  4. Choose “Internet Protocol Version 4 (TCP/IPv4)” and click Properties again.
  5. In the window that pops up, select “Use the following DNS server addresses”.
  6. Enter these values:
    • Preferred DNS server:
    • Alternate DNS server: DNS IP To Google's Public DNS
  7. Click OK to save your changes.

For Mac OS:

  1. Go to System Preferences on your Mac and select the “Network” panel under Internet and Wireless.
  2. In the Network preferences, pick your current network (like Airport or Ethernet) and click “Advanced”.
  3. Choose the DNS tab.
  4. To add Google’s DNS servers, click the “+” button.
  5. Enter these DNS server addresses:
    • Preferred DNS server:
    • Alternate DNS server: DNS IP To Google's Public DNS
  6. Click OK to apply the changes.

Solution #6: Disabling DNS Prefetching

DNS prefetching is a nifty browser feature aimed at speeding up webpage loading by anticipating and resolving domain names before they’re actually needed. With it turned on, your browser guesses which links you might click and gets ahead of the game by resolving those domain names in advance. This can cut down on the time it takes to load pages. However, sometimes it can backfire, leading to headaches like network errors. This hiccup can happen if the browser messes up the prefetching or if there are problems with the DNS server.

Disabling DNS prefetching can be a lifesaver in such situations. It stops the browser from trying to second-guess your network actions. Instead, it only resolves domain names when you explicitly ask it to, potentially sidestepping any errors in the prefetching process and giving you a smoother browsing ride.

To disable DNS prefetching in Chrome:

  1. Open Chrome and click on the three-dot menu icon in the top-right corner.
  2. From the dropdown menu, select Settings.
  3. Scroll down to the bottom and click on “Show Advanced Settings”.
  4. In the Privacy section, find the option labeled “Predict network actions to improve page load performance”.
  5. Uncheck the box next to this option to disable DNS prefetching.
  6. Once done, close the Settings tab.

Disabling DNS Prefetching

Solution #7: Disabling DNS Prefetching

Firewall toon

One of the things you should investigate is your operating system’s Firewall settings. These bad boys act like bouncers at a club, deciding who gets in and who stays out. If they’re too strict, they might just kick Chrome to the curb, leaving you scratching your head with an ERR_NAME_NOT_RESOLVED error.

To get to the bottom of this, dive into your operating system’s firewall settings. If you’re on Windows, head to the Control Panel; if you’re rocking a Mac, it’s in System Preferences. Once you’re there, take a peek at the rules and make sure Chrome has the green light to chat with the internet. If need be, you can even give the firewall a timeout by temporarily disabling it to see if that sorts things out.

But wait, there’s more! Your Antivirus software could also be in on the shenanigans. Sometimes these programs double up as wannabe firewalls, and if they’re feeling a bit too trigger-happy, they might block Chrome’s connections by mistake. To suss out if this is the case, consider hitting pause on your antivirus program temporarily and see if Chrome behaves.

So, by tinkering with your firewall settings and giving your antivirus program a break, you might just crack the code on those pesky Chrome connectivity issues. Just don’t forget to re-activate your firewall and antivirus once you’re done playing detective—we wouldn’t want any unwanted guests crashing the party.

Solution #8: Internet Connectivity Issue

Internet connectivity is like the heartbeat of modern computing—it keeps everything ticking along, from work to play. But when you hit snags like this dreaded network error, it’s time to roll up your sleeves and dig into those internet settings to keep the flow smooth.

Start by giving your internet settings a once-over to make sure no sneaky proxy configurations are messing things up. Proxies can throw a wrench in the works, making it tough for your browser to reach the sites you need. If you spot any proxy settings lurking around, it’s time to kick them to the curb.

Next up, the good ol’ restart trick can work wonders, especially for your modem or router. These trusty devices can sometimes get a bit glitchy or struggle with connectivity issues over time. A quick reboot often sorts them out, getting your internet back up to speed in a jiffy.

Now, if you’re dealing with a telephone broadband connection, things get a tad trickier. That static noise on the line? Yeah, that’s not a good sign. It could mean trouble brewing beneath the surface, messing with your internet connection. Check all your connections carefully and give them a snug tightening. If the problem sticks around, it’s probably time to call in the cavalry—your Internet Service Provider (ISP). They’ve got the know-how to tackle these kinds of issues and get you back online pronto.

So, whether it’s tweaking those internet settings, giving your gear a reboot, or tackling telephone line troubles, you’ve got the tools to troubleshoot like a pro and keep that digital world within reach.


  1. It is possible that there is something wrong with your router that creates the error. You can power cycle your router to see if it is helpful.
    a) Shut down your router completely and unplug the power cable from your router.
    b) Leave it for a few minutes.
    c) Plug the cable back and turn on the router. Check and see if the problem resolves.
    Solution 4: Check your modem router


Please enter your comment!
Please enter your name here