Hit enter to search or ESC to close
When you see an error in the browser, it is undoubtedly a frustrating experience. For starters, it gets in the way of your browsing time, but more than that, fixing an error can be a hassle. One reason for this is that a browser-related issue, such as a DNS_PROBE_FINISHED_BAD_CONFIG error, is actually a problem with your computer.
Very often, the solution is to change some of your computer’s settings to fix the problem. For example, you’ll take a look at your browser and Domain Name System (DNS) cache, and dig into your network drivers. The good news is that each fix is straightforward to implement.
For this post, we are going to show you how to fix DNS_PROBE_FINISHED_BAD_CONFIG error. There are many ways that can help, and we’ll cover them all. First, we are going to talk about what the error is, and why it appears.
For those unaware, DNS helps users access the correct website after entering the domain name in the browser. It takes the domain name itself, does a ‘lookup’ on the database for Internet Protocol (IP) addresses, and routes the user to the correct server.
For example, if you wanted to navigate, you would type this into the browser. Under the hood, the browser initiates a request for DNS, which in turn finds the corresponding IP address and makes the connection. As an end user, you won’t see any of this under most circumstances. You should notice a seamless transition from entering the domain name to viewing the website.
However, in some cases, you will get a DNS error. There are a few different ones with specific reasons:
In detail, DNS_PROBE_FINISHED_BAD_CONFIG is a network connection error that means there is a problem with the DNS configuration settings. Take a look at the next section for what this means in specific terms.
Because there is a configuration issue with your DNS, this is going to be the common cause of the error. To be specific, there are several reasons why you might see the DNS_PROBE_FINISHED_BAD_CONFIG error:
The main reason behind the DNS_PROBE_FINISHED_BAD_CONFIG error is a network, which often happens on your own computer. As a result, we can focus our attention here in a few different ways.
To fix DNS_PROBE_FINISHED_BAD_CONFIG error, you will mainly work with your computer’s system. In many cases, the improvements are straightforward, although there are others that require more technical consideration:
Of course, the first thing to do is to make sure that the DNS_PROBE_FINISHED_BAD_CONFIG error is not a temporary fault. So we will start from here.
An article on browser errors wouldn’t be complete without the polite term ‘pre-game’, in which to check out some basic ‘IT technical support’ points. Therefore, we urge you to try the following before you start digging deeper into your system’s settings:
If you check all these boxes and you still have the DNS_PROBE_FINISHED_BAD_CONFIG error, there is much more you can do. We’ll cover all of the methods we recommend in the rest of this article.
A ‘swap’ or temporary file is a common feature to almost every system. In most cases, your computer will have a ‘garbage collection’ system, where it removes these temporary files after a certain period of time. Whether that point isn’t here yet, or trash hasn’t happened for some files, you’ll want to take matters into your own hands.
If you are a Linux user, the Temporary Files folder is emptied automatically when the system reboots, so you are good to go. However, for Windows and macOS users, there are a few steps to take.
Starting with Windows, if you type “%temp%” into the search bar, it will open the corresponding directory:
The simple thing to do here is to select them all and clear the folder.
For macOS machines, press slip away , order , Yes shortcut to open go to folder conversation. navigate here ~/Library/Cache,
you may want to press slip away , order , Period To show all hidden files, as this will help you capture everything. Regardless, you’ll come across a folder full of temporary files:
Again, select everything and delete the content. If this step doesn’t help you fix the DNS_PROBE_FINISHED_BAD_CONFIG error, someone else can do it.
To be honest, your browser cache may not be the primary cause of the DNS_PROBE_FINISHED_BAD_CONFIG error, but it won’t hurt your chances of fixing it.
First, the bad news: Each browser has its own process for clearing the cache. The good news, however, is that we cover this in depth on the Design Bomb blog. Also there are a lot of tutorials that refer to clearing the browser, such as how to fix White Screen of Death (WSoD).
Whatever your browser is, try to clear the cache and check for DNS errors again. If the error persists, then at least you have a clean slate to look at other options.
Of course, if the DNS_PROBE_FINISHED_BAD_CONFIG error is due to a problem with the DNS, you’ll want to rule out this aspect. Your computer will use the DNS cache for the same reasons that the browser cache exists. However, like other caches, you can find old files that may be causing you problems.
Linux users again have a simple way for this: open the command terminal using Control , slip away , TeaThen run the following:
sudo systemd-resolve --flush-caches
For Windows users, it’s only a little more complicated. First, open Command Prompt – you can type “cmd” in the Windows search bar to find it:
here, type ipconfig /flushdnsand press enter to run the command:
For macOS, see Open a Terminal window (often using Spotlight or navigating to it) Applications > Utilities > Terminal Screen:
type from here sudo killall -HUP mDNSResponder, then run the command. You may not see a confirmation message in any of these cases, but the process will go on. Feel free to check if the DNS_PROBE_FINISHED_BAD_CONFIG error is gone, but don’t close these Terminal and Command Prompt windows just yet: Here’s something else you can do to fix the problem.
sudo killall -HUP mDNSResponder
Your IP address is a central part of DNS, so you can also modify it to fix the DNS_PROBE_FINISHED_BAD_CONFIG error. In Windows, go back to your Command Prompt, and type the following commands, running each one in turn:
The first command will drop the lease for your IP address, and the second one will obtain a new one. It will help to delete and restore the cached information for your IP address, and it takes a few seconds to do.
For macOS, you can go to System Preferences > Network Screen:
The option you need is below advanced section, under TCP/IP tab. click here Renew DHCP Lease,
This will yield the same result as Windows, and again, you may not get a confirmation that the process is successful.
Your Internet Service Provider (ISP) will provide you with a DNS server, and 99 times out of 100, you won’t need to think twice about it. However, once you need to consider this, you can change your DNS settings and resolve the DNS_PROBE_FINISHED_BAD_CONFIG error.
For macOS, it’s a snap. head first System Preferences > Network screen, in advanced section, and see the DNS tab:
You can add a new DNS server by using plus icon under dns server List. There are lots of public and private DNS servers you can use. However, if you want to test whether this will resolve the DNS_PROBE_FINISHED_BAD_CONFIG error, you can use CloudFlare’s public DNS servers 188.8.131.52,
For Windows, you can go to the Settings screen, and look for Network & Internet:
Next, search change adapter options link, and go to that screen:
it you Network Connection page, which will list all the connections to your system. Your task here is to right-click on your chosen connection, and head to Property Screen:
Property The screen will show a list of different protocols. Choose Internet Protocol Version 4 (TCP/IPv4) options, and click Property button:
The last step is to choose Use the following IP address radio button. In the IP Address field, enter your chosen DNS server:
Once you have confirmed your changes, you can check for the DNS_PROBE_FINISHED_BAD_CONFIG error – it will disappear if all goes well.
This may be surprising, but most users will face many browser errors on a daily basis. The humble 404 error is one, but in-browser errors can stop you in your tracks. In many cases, this will be literal, as you won’t be able to browse to a specific website until you’ve fixed the problem.
The DNS_PROBE_FINISHED_BAD_CONFIG error is one such case, and this post describes how to resolve it. Overall, make sure you have solid physical connections, clear your browser and DNS cache, work with your DNS settings, and renew your IP address. One (or a combination) of these will work, and from there you can return to browsing the web.
About the author