How to Fix the DNS_PROBE_FINISHED_BAD_CONFIG Error Code (Ultimate Guide)

Sometimes when you try to open a website, it doesn’t work. Instead, you get a message that says DNS_PROBE_FINISHED_BAD_CONFIG. That can be really confusing if you don’t know what it means.

This just means your computer had trouble finding the website. Every site has a special address called an IP address. Your computer uses something called DNS to figure that out. If DNS doesn’t work right, the website can’t load.

The good thing is this problem isn’t usually a big deal. You can try a few things and it might be fixed pretty fast.

In this article, I’ll tell you what this error means and why it might happen. Then I’ll show you some steps to fix it. Some are easy, and some take a bit more time, but you can go one step at a time.

Let’s begin.

What Is the DNS_PROBE_FINISHED_BAD_CONFIG Error?

Like I said earlier, this error creeps up when your device can’t connect to a website because something’s wrong with how it finds website addresses.

Usually, the problem comes from one of these:

• Your device’s network settings are off
• Your Wi-Fi router is being glitchy
• Your internet provider’s address book (DNS) is having issues

To figure out what’s causing it, it helps to understand what DNS is and why it’s important when you’re trying to load any website.

Understanding DNS and Its Role in Website Access

DNS is basically the internet’s phone directory. When you type in a website name (like google.com), DNS is what turns that into the actual number (IP address) where the site lives.

Here’s the catch—if this translation fails, your browser gets stuck. It’s like asking for directions to a restaurant and being told “I don’t know” by every person you ask.

What the Error Message Means in Plain Terms

When you see this error, it means:

1. Your device asked “Where’s this website?”
2. The DNS system either gave wrong directions or didn’t answer
3. Now your browser is stranded with nowhere to go

The good news?

It’s usually easily fixable and isn’t typically a sign of serious damage.

Why It Appears in Chrome, Firefox, Safari, and Edge

This isn’t about your browser, it’s about what happens before your browser even gets started. Whether you’re using Chrome, Firefox, or anything else, they all rely on DNS working correctly first.

Same goes for your device: Windows PCs, Macs, Androids, and iPhones can all run into this because they all use DNS the same basic way.

What Triggers the DNS_PROBE_FINISHED_BAD_CONFIG Error?

There are different factors that can cause this error and many can easily be overlooked. In most situations, the issue at hand can be either local configuration errors or something that is disrupting the device’s connection to the DNS servers.

Below is a list of the most common culprits:

Local Device Issues

Sometimes the problem starts right on your machine. A few examples:

• Network settings that are configured incorrectly: If you change your DNS or IP settings manually, this may prevent access to some connections or functionality. If the details are wrong your system will not know what to do if it gets domain name requests.
• Outdated DNS cache or temporary files: Devices temporarily save information about DNS records to improve browsing speed. Old or corrupted cache can also result in resolution failures. Deleting it generally will resolve the problems.
• Corrupted system files or drivers: Sometimes, corrupted files or old network drivers can interfere with basic connectivity, and can specifically interfere with the functionality of DNS requests, their collation, and your OS’s functionality.

Software Conflicts

Some programs designed to protect or optimize your system might actually interfere with DNS traffic.

• Antivirus or firewall blocking DNS requests: Security software can mistakenly treat DNS queries as suspicious traffic. If they block those requests, you’ll see connection errors.
• VPN or a proxy interfering with DNS resolution: Some servers that reroute your internet traffic will override your default DNS settings. If their servers get interrupted, your browser cannot find the site.

Network & ISP-Level Issues

If everything seems fine on your device, the problem is likely stemming from your router or your service provider.

Some possible problems include:

• DNS server downtime: If an Internet service provider’s DNS servers are simply down temporarily, your device will not have any way to resolve domain names.
• DHCP Router Conflicts: DHCP provides devices with IP addresses on your network. If the router’s router has a misconfiguration or a conflict, it could create a DNS and make this error possible.

Browser-Level Issues

While this error is not actually caused by your browser, certain browser-related problems can make it worse or trigger it under the right conditions.

• Outdated browser: An older version of a browser has a greater chance to mess up DNS fallbacks, especially when it is working with new networking protocols.
• Extensions: Some extensions can affect network behavior. In particular, the ad blockers, privacy tools, or VPN extensions can impact the routing or resolving of DNS queries.

How to Resolve the DNS_PROBE_FINISHED_BAD_CONFIG Error (Step-by-Step Solutions)

Easy Fixes

Before we investigate more in-depth possibilities, it’s always smart to try some easy troubleshooting steps.

If you have determined if the problem really is with you, rather than your Internet provider, or the website you are trying to get to, let’s get started with the easiest, least-technical fixes first.

1. Restart Your Router and Computer

In certain cases, the simplest fix is the best fix. Restarting your router and computer can resolve temporary glitches or misconfigured network settings.

Here is what you need to do:

• You need to turn off your router, which usually can be done by unplugging it from the wall. Wait at least 30 seconds before plugging it back. This should give it enough time to fully reset where it comes to any cached settings.
• While it reboots, restart your computer. This should clear out any stale configurations or temporary network glitches on your side.
• After both devices are back-on, try accessing the website again.

If it was just a simple DNS Conflict or glitch related to IP assignment, this quick reboot should solve the problem easily.

2. Reload the Website or Try Incognito Mode

Another quick fix you can try is to reload the website or open it in an incognito window. It sounds basic, but a lot of times, the browser just hiccups — maybe something’s off with the cache or a recent tab didn’t load right.

If a quick refresh doesn’t do the trick, jump into incognito mode. That way, your browser skips over saved data like cookies and extensions, which can sometimes mess with DNS.

If the site opens fine there, you’ve likely got something in your browser — maybe an extension or cached file — causing the issue.

3. Clear Browser Cache and Cookies

Old cache files or cookies can sometimes mess with how your browser connects to websites. These bits of stored data are meant to speed things up, but they can also hold onto outdated information that causes conflicts—especially with DNS settings.

To rule this out, in Chrome:

• Click the three-dot menu → Settings
• Go to Privacy and security → Clear browsing data

• Select Cached images and files and Cookies and other site data

• Hit Clear data

After that’s complete, restart your browser and revisit the site. If the site loads properly now, stale data is likely the problem.

4. Disable Suspicious Browser Extensions

Some browser extensions—especially VPNs, ad blockers, or security-related tools—can sometimes mess with how your browser connects to websites. If you’re seeing the DNS_PROBE_FINISHED_BAD_CONFIG error, an overactive or buggy extension might be the culprit.

Here’s how you can check:

• Open your browser’s extension or add-on settings
  In Chrome, click the three-dot menu in the top-right, go to Extensions > Manage Extensions.

• Turn off all active extensions
  Toggle each one off, or remove them entirely if you don’t recognize them.

• Reload the website
  Try loading the site again with all extensions off. If it loads fine, you know one of them was causing the problem.
• Re-enable extensions one by one
  Switch them back on gradually to figure out which one triggered the error.

Once you spot the one creating issues, consider removing it or finding an alternative.

5. Update Your Browser

Believe it or not, your browser could be the reason you’re running into weird DNS issues. You might not notice anything odd while browsing normally, but if it hasn’t been updated in a while, it can trip up on modern websites. Stuff like DNS_PROBE_FINISHED_BAD_CONFIG can happen just because your browser is out of step with today’s web.

Here’s what to do:

Open up your browser (Chrome, Firefox, whatever you’re using). Look for those three dots or three lines in the upper right corner. In there, look for Help or About options. If you’re using Chrome, it’ll say “About Google Chrome.” Firefox has “About Firefox.”

Click that, and your browser should automatically start checking for updates. If one’s available, it’ll give you a button or prompt to install it. Let it finish. Then go ahead and close the whole thing and reopen it.

This should hopefully fix the issue. If not, move to more advanced troubleshooting methods which we’ll cover next.

Intermediate Fixes

If the quick tips didn’t work, don’t worry. There are a few more things you can try that dig a little deeper into how your system handles internet connections.

1. Flush DNS Cache

Sometimes your device holds on to old website data, and that can lead to DNS errors. Clearing the DNS cache forces it to look up fresh info.

On Windows:

• Click the Start button, type cmd, right-click Command Prompt, and pick Run as administrator

• In the black window, type this:
• ipconfig /flushdns
• Hit enter and you should see this message: Successfully flushed the DNS Resolver Cache\

On macOS:

• Open Terminal
• Paste this line:
• sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
• Press enter, then enter your password when prompted

That’s it. Once done, close everything, reopen your browser, and see if the issue is gone.

2. Renew Your IP Address via Command Line

If flushing the DNS didn’t help, the next thing to try is renewing your IP address. This can clear up any leftover network issues your system’s holding onto.

On Windows:

• Click the Start button, search for “cmd”, right-click Command Prompt, and select Run as administrator.
• Type ipconfig /release and hit enter.

• Once that finishes, type ipconfig /renew and hit enter.

• Wait for the command to finish, then close the window.

On Mac:

• Go to System Settings and open Network.
• Select the connection you’re using (Wi-Fi or Ethernet).
• Click Details or Advanced.
• Under the TCP/IP tab, hit Renew DHCP Lease.

Give your browser another try after that. If things still aren’t working, don’t worry — we’ve got a couple more steps that might do the trick.

3. Manually Change DNS Settings (Google or Cloudflare)

Sometimes your internet’s working, but websites still won’t load — that’s often a DNS issue. DNS is what helps your browser find the actual server behind a web address. If your current DNS is slow or buggy, switching to a faster public one can fix the problem.

On Windows:

• Open the Control Panel.
• Go to the Network and Sharing Center.
• Click Change adapter settings on the left.

• Right-click your connection > Properties.

• Double-click Internet Protocol Version 4 (TCP/IPv4).
• Choose Use the following DNS server addresses.
• Use one of these sets:
  • Google: 8.8.8.8 / 8.8.4.4
  • Cloudflare: 1.1.1.1 / 1.0.0.1
• Click OK and restart your browser.

On macOS:

• Open System Settings > Network.
• Select your connection and hit Details.
• Go to the DNS tab.
• Add the DNS addresses above.
• Apply the changes.

Public DNS tends to respond faster than what your ISP gives you. If sites start loading again after the switch, the DNS was likely the issue.

Advanced Fixes

If nothing has worked so far, it’s time to go a step further. Let’s now check out some advanced troubleshooting steps, starting with removing temporary system files that may be interfering with how your computer connects to websites.

1. Remove Temporary System Files

We’ve already talked about cache and DNS data earlier — but if you’re still facing the error, a full cleanup might help. This includes clearing out any lingering system files that could be interfering in the background.

On Windows:

• Open the Run dialog with Win + R
• Type cleanmgr and press enter

• Choose your system drive (usually C:)
• Select Temporary Files and any other non-essential options
• Hit OK and confirm deletion

On macOS:

• Go to Finder > Go > Go to Folder
• Type ~/Library/Caches
• Carefully delete only system-related cache folders
• Empty your Trash

Once done, restart your device to flush any remaining data. This should resolve the DNS_PROBE_FINISHED_BAD_CONFIG error.

2. Disable Antivirus or Firewall Temporarily

Sometimes, your security software might be blocking your connection without warning. It’s worth turning it off briefly to check.

On Windows:

• Open your antivirus program
• Look for a pause or disable option — most have one on the main screen
• To disable the firewall, go to Control Panel → System and Security → Windows Defender Firewall
• Click “Turn Windows Defender Firewall on or off”

• Choose “Turn off” for both private and public networks

On Mac:

• Open System Settings
• Go to Network → Firewall
• Switch the firewall off

Try loading the site again. If it works, the issue’s likely with your security tools. You can either tweak their settings or add exceptions for your browser or DNS. Just don’t forget to turn protection back on afterward.

3. Disable Proxy Settings or VPNs

DNS issues can also be caused by a proxy or VPN that’s active in the background. These tools can reroute your connection, and while that’s great for privacy, it can also cause conflicts with DNS settings.

On Windows:

• Open Settings
• Go to Network & Internet > Proxy
• If “Use a proxy server” is turned on, switch it off
• Then check the VPN tab and disconnect any active VPNs

On macOS:

• Open System Settings and select Network
• Choose your active connection
• Click Details (or Advanced) > Proxies
• Uncheck any enabled options
• Save and exit

If you’re using a VPN app, shut it down fully—don’t just minimize it. Then, reload the page that was giving you trouble. If DNS was getting rerouted in a way your system didn’t like, this usually clears it up.

4. Update Network Adapter Drivers

Updating your network adapter driver is also a quick fix that can help resolve the issue. These drivers control how your system connects to the internet, and if they’re outdated or corrupted, DNS errors can crop up unexpectedly.

On Windows:

• Press Win + X and select Device Manager
• Expand Network adapters
• Right-click your active adapter (usually labeled “Wireless” or “Ethernet”)
• Choose Update driver
• Select Search automatically for drivers

If Windows says the best driver is already installed, it’s still worth checking your device manufacturer’s website for a newer version.

On macOS:

• Head to System Settings > General > Software Update
• Install any pending updates
• Restart your Mac once done

A fresh driver install can quietly clear up a lot of background network conflicts — including this DNS error.

For Website Owners: Checking Your Own DNS (Just in Case)

Most of the time, DNS_PROBE_FINISHED_BAD_CONFIG is a local issue — caused by something on the visitor’s end, like their device or network. But if you’re hearing about it from multiple people, it’s smart to take a minute and rule out any DNS issues on your side.

You’re probably fine — but it never hurts to check:

• A Records – Your root domain and www should both point to the right IP.

• CNAMEs – Make sure subdomains like blog.yoursite.com still work.

• Name Servers – Check that you’re using the right ones from your registrar or host.

• Propagation – If you made recent changes, a tool like whatsmydns.net helps you see if everything’s live worldwide.

Just a few quick checks, and you’ll know for sure everything’s set up right.

If you host with us at Cloudways, and use our DNS Made Easy addon, you can manage DNS records directly inside your dashboard. It helps keep things running smoothly and reduces the risk of downtime from DNS missteps.

Wrapping Up!

If you’ve run into the dns_probe_finished_bad_config error, you’re not alone. It’s a common problem, especially on Chrome, though it can show up in any browser. In this blog, we broke down what causes this error.

We covered a range of solutions — from clearing cached settings to switching your DNS to more reliable options like Google or Cloudflare. In some cases, DNS issues on the website owner’s side can also cause this error, and we shared ways to identify and address that too.

Hopefully, one of these fixes worked for you. If not, drop a comment below and I’ll be happy to help. And if you’re a Cloudways customer facing DNS-related issues, our 24/7 support team is always ready to assist you.