Errors that comes because of some basic issues or conflicts with DNS that never good, because they are hard to resolve. Errors like dns_probe_finished_bad_config or also known as DNS PROBE FINISHED BAD CONFIG is the error that is hard to resolve because there can be multiple reasons for this error.
This leads to confusion among the trouble-shooter as there is no any easy way to explain what is wrong with the internet. The basic and easiest way is to start the entire process is by making sure that your internet is actually working on other devices.
Fix DNS Probe Finished Bad Config Error
It is quite useful trick because it could easily save a lot of time troubleshooting. Calling the professional and having them fix and it will resolve the dns_probe_finished_bad_config error. If not, then you need to start the troubleshooting yourself by following the below tried and tested methods.
Why DNS Probe Finished Bad Config error comes in Google Chrome?
Over the course of the last of couple of years, there have been a lot of questions regarding the origin of the infamous error. You need to understand that this error is quite prolific and confusing, to begin with, and to start, it exists under completely different names in many browsers.
So, if you are getting DNS PROBE FINISHED BAD CONFIG in Google Chrome, the same error might come completely different in a different browser. The one thing we certain about is that this error has something to do with DNS.
Now tons of people do not know this but DNS works in rather simple to understand way. It is not that much hard but still it is up to you that how you make sure that you are aware with this issue.
The main purpose of DNS is to translate the name of a website from our language to a language that internet can understand. So, for starters, if you type in www.google.com, the DNS will have to translate that into a machine-readable IP address.
How to fix DNS Probe Finished Bad Config error?
The methods to fix the different DNS errors are mostly same but to keep things relevant and fresh, we are going to provide different methods that may fix the internet, and fix the ever so dreadful dns probe finished bad config error.
Method 1: Restart Your Router
It may come as a surprise but not many are aware of the fact that restarting you’re hard restarting your router can fix the slew of DNS errors. It is because upon restarting, you’re cutting off all the communication between the router, the internet, and your computer.
So, when it turns back on again, the connection gets established again, giving it a chance to connect easily. It is very simple yet effective way to find out whether or not the internet is working properly.
In case of the internet starts working after the router restart, you will have no need to proceed with other methods, the methods we are discussing in this article are more advanced now.
Method 2: Fix DNS_PROBE_FINISHED_BAD_CONFIG Using CMD
Command prompt is the perfect solution for several issues that arise in Windows. While it may look like it is only for networking issues, the command prompt can help you with a broad issues.
One issue is the infamous “dns_probe_finished_bad_config”, if you are facing this error on your Google Chrome, you can try and resolve it by using some handful commands. The commands will eliminate the DNS in exchange for new that is functional.
Below we have added the steps to taken to perform the command prompt:
- Open the start menu, and type cmd, once the command prompt appears, right click on it, and choose Run as Administrator.
- Now you are going to have to run six different commands, one by one. Start off by running the following command.
- ipconfig /release
Press the enter key, followed by the second command.
- ipconfig /all
Repeat the same process and move on to the third command.
- ipconfig /flushdns
The command above will flush your DNS. Once that is done, you can renew your DNS by entering the following command.
- ipconfig /renew
The DNS is renewed, but there are still two more commands to go. Type the following command, and press enter.
- netsh int ip set dns
Lastly, enter the command below and close the command prompt once the command is registered.
- netsh winsock reset
Now you need to restart your PC, and once that is done, the DNS PROBE FINISHED BAD CONFIG error that should no longer have an issue. If for some reason, the error does not go away, you can try other methods.
Method 3: Try Disabling VPN Software
Since the DNS_PROBE_FINISHED_BAD_CONFIG is actually about DNS, the error can sometimes exist outside Google Chrome as well. During my testing, and exploration, we have come to realize that VPN is one of the culprits behind this error.
Sometimes when you turn the VPN off, or when you turn it on, it leaves a hit on the internet. This means that you may not get internet service after you may have enabled the VPN, or disabled it.
There are no steps to take here, so keeping that in mind, and you can simply turn off the VPN and see if the internet starts working after that.
We have been told by lot of people how they do not like to deal with the DNS errors just because they are random nature. Well it is important that you deal with the errors because a working internet is something everyone wants to have.
Sure, the DNS error you are facing might because of a lot of different reasons, and if you are facing this on a weekend, troubleshooting is all you can do. As annoying the DNS PROBE FINISHED BAD CONFIG error is, fixing the error is rather easy when you know what are you doing.
So if you like this guide than please share it with your friends and family.