The error DNS_PROBE_FINISHED_BAD_CONFIG sometimes happens in the browser when you need to use the internet, surfing the internet etc., This kind of error occurring in the browsers is quite common but not need to worry much about it, as it can be resolved. This kind of DNS errors happen due to the misconception of the DNS server which is never good and it has to be troubleshooted to have a good working internet connection to make use of the internet surfing without any interruption.
Let us see/learn some technical stuff briefly to understand the cause of the DNS_PROBE_FINISHED_BAD_CONFIG error in Google Chrome, process to troubleshoot and maintain a good working internet connection. You can also check out, fixing DNS_PROBE_FINISHED_NXDOMAIN on Google Chrome.
How To Fix DNS_PROBE_FINISHED_BAD_CONFIG in Chrome
What is DNS?
DNS is the abbreviated form of “Domain Name System” which converts the manually given alphabetical name the websites into the numerical machine understandable IP address. It has the database of all IP address, which redirects to the specific website assigned to it. Your DNS server has all the database similar to the telephone directory which we used to refer for searching someone’s telephone number. This is the main purpose of the DNS which is simple to understand. There is no rocket science behind this DNS, that many people are not aware of it.
The origin of DNS Error
As time goes by, for the past few years there were many questions roused regarding the origin of DNS errors. To make you understand in a transparent way, there is no specific reason for the DNS related error occurred. It is quite profuse and puzzling to start with. The error occurs in different names with the “dns_probe_finished_…….” for different browsers.
Unfortunately, the bad case is that there are different possible ways for the error that might occur due to your VPN settings, browser, DNS router, manufacturing cable or might even be your internet connection at the source.
Troubleshooting DNS_PROBE_FINISHED_BAD_CONFIG Errors
Keep in mind that dns_probe_finished_bad_config error in chrome happens when the DNS fails to translate the alphabetical URL into a machine-readable numerical IP address. The process of troubleshooting for all kinds of DNS error is almost same for all browsers. Here, we will let you know few processes to resolve the error. Try any of the given solutions to rectify the error. All the solutions given here are being tested and it is 100% working to resolve the DNS error.
Solution 1: Restarting The Router
One simple and easy way is to restart your router. Not everyone is aware of this, and it may even surprise you by just simply getting all the connections set off i.e.., no communication between your router, internet and to your computer. Let everything be stable for 5 to 10 mins. Then again make sure you are connected to it and once when it turns back if your error is resolved, the connection is established.
You can enjoy surfing internet. This is the easiest and simplest way to resolve the DNS_PROBE_FINISHED_BAD_CONFIG Fix error. If this does not work on your computer system try the other following solutions which are a bit technically advanced.
Solution 2: Flushing DNS Cache Might Fix DNS_PROBE_FINISHED_BAD_CONFIG
The dns_probe_finished_bad_config error can be fixed by using different command prompt like flush dns, renew, release etc.., also along with some important commands like resetting Winsock.
Step 1: Click on “windows” button from the left corner of your taskbar. In the search box type “cmd”,“ windows command processor” will be listed.
Step 2: Open the command prompt window (you will see a black screen window with your username of the system). Type & run the below-mentioned command one by one. You can even copy & paste the below-mentioned commands in the command prompt window.
netshintip set dns
NOTE: Run all the commands one by one. Do not copy all together and paste in the command prompt window. Wait until the command prompt finishes running the process.Once done, restart/reboot your computer system.
Solution 3: Change TCP / IPV4 Settings
Changing the TCP / IPV4 setting can also help you to resolve the problem. You can even try this option to resolve among other solutions by following the steps.
Step 1: Go to the windows button and select network connections.
Step 2: Now select the properties options from your current active internet connection.
Step 3: From the list of options select TCP / IPV4 settings and click properties.
Step 4: A new window will open. Just enter the given DNS setting in it. Change the preferred DNS server as 188.8.131.52 and alternate server as 184.108.40.206 and click ok.
That’s it. The process has been completed. Now you can go on surfing the internet.
Solution 4: DNS client – Restarting
Here is another solution to resolve the problem. It is simple and easy, within few seconds you can restart the DNS client.
Step 1: Press “Windows + R” keys together to open the run command window.
Step 2: Type “services.msc” and click ok.
Step 3: A new window will open with all the list of services. Scroll down until you see DNS Client.
Step 4: Right-click on the DNS CLIENT. You will have some list of options. Select Restart from the list of options. Your DNS Client will have successfully reset.
Solution 5: VPN Settings Might Fix dns_probe_finished_bad_config
There are no steps to carry out here. Just by changing your VPN setting OFF, you may get the internet connection again. This may happen while enabling/disabling VPN settings that may hit the internet. Simple turn OFF your VPN and check the internet connection.
Recommended: How To Fix ERR_SPDY_PROTOCOL_ERROR In Google Chrome
Final Thoughts to remember,
A good internet connection is what everyone wants for. dns_probe_finished_bad_config is not an error which is not impossible to resolve. With the little knowledge of what you are doing, try to troubleshoot the error with the help of this article. We have given all the necessary tips and fixes for which dns_probe_finished_bad_config in Chrome can be resolved. Try to stick with the same service provider. Do not change service providers often. Please write to us about your experience.