The DNS Probe Finished Bad Config error code that sometimes pops up with primarily Google Chrome and sometimes other browsers can be especially annoying since it is a little tougher to fix than just restarting your browser, most of the time.
DNS Probe Finished Bad Config error generally occurs when there’s a mistake within the configuration of your PC or router. That being said, it can also happen due to other reasons like faulty anti-virus software, problems regarding the website being down, and problems in your firewall settings.
Let’s take a look at what causes this dns_probe_finished_bad_config error message to generate and some different ways to correct the issue.
- 1 What is the DNS Probe Finished Bad Config Error Code?
- 2 What Causes the DNS Probe Finished Bad Config Error Code?
- 3 What Can You Do to Remedy the Error?
- 4 Solution # 1 DNS Flushing
- 5 Solution # 2: Manual Reconfiguration
- 6 Solution #3 Turning of Firewall and/or Antivirus
- 7 Solution #4 Resolving Website Filters
- 8 Conclusion
What is the DNS Probe Finished Bad Config Error Code?
This error code is generally generated when there is an issue with the connection to your PC or router to the browser. This is not an issue with solely the browser, but with the entire connectivity.
Due to this, it can be especially tricky to fix this issue, especially since you often do not know the exact source of the issue when trying to make the repair. Either way, there are some options to help you get back online.
What Causes the DNS Probe Finished Bad Config Error Code?
Generally, this code can be caused by a number of different things. Having faulty antivirus software is one of the leading sources since it can prevent a proper connection from forming.
Similarly, your firewall settings being skewed can cause similar issues, as well. Some also get it just when the website in question is down. It can come from a multitude of sources but, fortunately, the fixes are almost always the same.
That being said, if the website is down, there is not much you can do other than wait for it to come back up. To check if the site is the issue, try going to a different website that normally loads well for you.
If it loads, chances are the issue is with the website. You can also use something like Down Detector to check if the site is down, as well, if you are still unsure. Otherwise, you are going to have to go with one of the other remedies.
What Can You Do to Remedy the Error?
When remedying the DNS Probe Finished Bad Config error code, you have quite a few different options. You may be able to use any one of them to fix the issue or you may have to play around and figure out which one works for you. Either way, most people report success with these methods. Your Options Are:
1. DNS Flushing
As the most effective and widely used fix for the DNS Probe Finished Bad Config error, this is your best bet. Most people experience an immediate repair of their internet connectivity and can get back online directly after trying this method. It is also fairly easy to do.
2. Changing Antivirus or Firewall Settings
Sometimes your antivirus or firewall prevents a connection from forming. Changing your settings or turning off the antivirus or firewall can fix this issue and get you back online.
3. Manually Reconfiguring Your DNS
If the flushing and firewall and antivirus adjusting do not work, you may need to try to manually reconfigure your DNS settings. This is a little more complex but can help fix the issue and reconnect you.
4. Check for Hardware Issues
Sometimes, the issue is physical. Check and see if there are any hardware issues with your device.
5. Check for Site Blocks
Sometimes, extensions or updates on your browser can block certain websites. Check this and consider undoing the update or removing the extension if possible to fix the issue.
Solution # 1 DNS Flushing
This is most likely the most common fix for the dns probe finished bad config error. DNS Flushing initially deletes the existing DNS cache and then repopulates the settings. This way any out-of-date or faulty settings are replaced with proper settings thereby removing errors in DNS configuration.
To flush your DNS cache, follow these steps:
Open Command Prompt. To do that you can follow one of these methods
Press Windows+R and then type cmd.exe in the resulting search box and hit run.
Type “command prompt” in the start menu and hit enter.
Look for the command prompt in the accessories section in the program list.
Type the following codes in the resulting command prompt and hit enter after each code
Windows will now automatically reset the DNS settings and repopulate it with the correct settings thereby fixing the configuration problem. Check: How to Fix Google Chrome Not Responding
Solution # 2: Manual Reconfiguration
This process involves simple to try to do a manual reconfiguration of the DNS address. This is done by accessing the Network Sharing Centre (the button of which is found at the bottom right of the toolbar on your desktop).
Proceed with this method for a fast and straightforward manual overhaul of the network settings. The steps that you need to follow are:
Right-click on the network icon in the extreme right of the windows toolbar. It will be in the shape of a monitor if you are using LAN or the Wi-Fi symbol if you are using a Wi-Fi connection for internet.dns_probe_finished_bad_config fix
1.Select- “Open Network and Sharing Center.”
2.Select Local Area Network. On selecting. A new dialogue box will appear. Select
3.“Properties” as shown in the following image.fix dns_probe_finished_bad_config error
4.From the next dialogue box that opens, select “Internet Protocol Version 4” and press the ‘Enter’ button as below-easy methods to fix dns_probe_finished_bad_config error
5.After you have done those above, a new dialogue box will open. Select “Use the following DNS Server Addresses” as highlighted below.dns probe bad config error fix
Put the value- [220.127.116.11] in the Preferred DNS server and the value [18.104.22.168] in the
6.Alternate DNS server sections respectively.
Upon exit, you will need to check the “Validate settings” checkbox and press “OK.”
Following this, the way to fix dns probe finished bad config error should be resolved.
Solution #3 Turning of Firewall and/or Antivirus
The dns probe finished bad config error also can be as a result of any discrepancy in your system’s Antivirus, Firewall, or its related settings. If you’ve got started receiving the error after an update to your Antivirus software, or a change within the settings of your Firewall likelihood is that that this could be the root of your problems.
There is only one way of knowing for sure what the real cause of the error is and that is by turning off one of the two and checking if the error is resolved.
If turning one-off (while the other remains on) solves the problem then you have to restore the previous version of the software that is causing the problem. It is advisable to contact your vendor to get the software rectified. Also Check: the way to solve mobile network not available
Solution #4 Resolving Website Filters
Many website blocking extensions also cause the dns probe to finished bad config error. If you’ve got started having problems after installation or upgrade of any such software, consider disabling it temporarily or uninstalling it.
Check for the error again on your browser. If it works fine, then it was the software causing the issue.
Your browser’s dns probe finished bad config error, also can only be a result of a hardware malfunction. In this case, consider turning off your laptop or PC (or other related systems) and disconnecting it from all power sources.
Also, confine in mind that your LAN wire and/or router/DSL box should even be turned off and disconnected. Leave the whole system alone for five to10 minutes to make sure that the flow of electricity in your devices is completely drained. After this is often done, power on and reconnect the system and check if the error is displayed again.
Other Elementary Fixes
You can also try these quick alternates just in case your problem isn’t resolved. Keep your network driver updated. Out of date drivers can often be incompatible or erroneous and thereby end in the matter.
These quick alternatives include:
Erasing Browser Temp files & cache
Erasing browser history
The above methods can also solve the problem.
Try a different browser altogether.
It is always advisable to keep more than a single browser on your PC since the malfunctioning of one will not affect your work.
Uninstall the browser to show the dns probe finished bad config error, and reinstall it back.
It is always advisable to keep track of any update or changes that you make to your device. Keeping a track can help you identify target areas and loopholes quicker. It can also help you decide which solution to choose.
The primary step is to down any alterations made to the system, updates, or new software installations. You might also want to check your hardware connections.
The dns probe finished bad config error is often solved quicker once you have properly realized which step you’ve got to undertake. Often decisions taken in a hurry can worsen the situation. Thereby, it’s important to not panic and analyze all.