DNS PROBE FINISHED BAD CONFIG | How to Fix the Chrome Error in 1 Minute
DNS PROBE FINISHED BAD CONFIG is one of the most annoying DNS related errors mostly encountered in Chrome Browser. There are numerous reasons for which the DNS error occurs. And, the one you are facing could be for one or more reasons.
When the Chrome error occurs, your browser window will show a page crash message saying “This webpage is not available” with a tagline DNS_PROBE_FINISHED_BAD_CONFIG.
Which means, there is a bad configuration issue with DNS in the browser. And, the DNS failed to convert the domain name into its relevant IP address.
Thus, the website you are trying to access will show the error message instead of its contents.
So, how do we fix it? Well, before we do of course fix your DNS problem, I would like to have a look at the possible reasons behind the DNS PROBE FINISHED BAD CONFIG in Chrome.
Best 7 Fixes for DNS Server Not Responding In Windows 8/8.1/10
Well, before we do of course fix your DNS problem, I would like to have a look at the possible reasons behind the DNS PROBE FINISHED BAD CONFIG in Chrome.
Reasons of DNS_PROBE_FINISHED_BAD_CONFIG in Chrome
As I have mentioned earlier, if DNS faces any interruption in converting a domain name into IP address, the error takes place. Now, what reasons can possibly lead to your DNS error? Let’s check that out.
- Your Chrome Browser might have failed to communicate with DNS server.
- The DNS server could be down at that certain time.
- The Firewall of your computer might have blocked DNS server to prevent malicious website access.
- Your Computer might be virus corrupted.
- And, your Internet connection could be unstable.
How to Fix DNS PROBE FINISHED BAD CONFIG Error in Chrome Browser?
Keeping in mind all the possible reasons of DNS_PROBE_FINISHED_BAD_CONFIG in Google Chrome, I have listed out the best solutions that worked precisely for me. I hope, these solutions will help you out as well.
First of all, you will need to check your Internet connection whether it is working properly or not. Check your Power Cycle connectivity if you are using any Router or Modem.
Once you are confirmed that your Internet connectivity is good, you may try out the following fixations.
Fixation 1: Delete Outdated Browser Cache and Cookies
Sometimes, outdated cache and cookies of your browser can cause DNS server act funny. So, clearing the old overwhelmed browser caches can be a good idea. Follow the below steps to get it done.
- Click on Chrome browser “More” options located at the top right corner of the tab.
- Navigate your mouse cursor to the “More tools” followed by clicking on “Clear browsing data” option.
- Now, click to checkboxes of “Cached images and files” and “Cookies and other site and plugin data” option.
Note: Don’t checkbox the other options such as “Browsing history,” “Download history,” “Passwords,” etc. if you don’t want to lose them.
- Finally, click on the “Clear browsing data” option to execute the action.
Once your browser cookies are cleared, ou may try accessing the website you wish to. If the error still persists, try the next fixation to resolve the issue.
Fixation 2: Disable Windows Firewall
To check and fix if your Windows Firewall is interrupting the DNS server to carry out its usual job, follow the below procedure.
- Go to your system “Control Panel.”
- Now, click on the “System and Security” option.
- Click on “Windows Firewall” option.
- Next, locate and click on the “Turn Windows Firewall on or off” option.
- Now, click and “Turn off Windows Firewall” for both Private and Public networks.
I hope this fixation will work. If don’t, follow the next fixation.
Fixation 3: Change DNS Address
The DNS server address on a network is created automatically by your server. In some cases, the existing server address fails to work properly, it is better to change the address. Follow the below instruction to do it so.
- Right-click on the Network icon located at the right corner of your Computer Taskbar.
- A pop-up will appear containing two options. Click on the “Open Network and Sharing Center.”
- Click on the active “Internet” connection your currently connected with.
- Now, a pop-up window will appear. Click on “Properties” button.
- Enable the “Internet Protocol Version 4 (TCP/IPv4)“option on the next window and hit the “Properties” button again.
- Enable the “Use the following DNS server address:” option.
- Now input the following DNS Server addresses.
Preferred DNS server: 8 8 8 8
Alternate DNS server: 8 8 4 4
- Now, enable the “Validate settings upon exit” option and hit “OK” button to execute changes.
Hitting on that OK button will make sure the changes on your DNS server address. You may now check your error once again whether it is gone or still eating up your mind.
Unfortunately, the above fixations do not work, I have got more solutions for your right here. Peace.
Fixation 4: Flush and Renew DNS Cache
Flushing and renewing DNS caches is one of the most effective solutions to any error in related to Chrome browser including DNS Probe Finished Bad Config. So, below here is how you will fix the DNS_PROBE_FINISHED_BAD_CONFIG error.
- Run Command Prompt as your administration. Windows start > type “cmd” > hit Enter key.
- Once the command prompt window is ON, you must input the below codes one by one and hit Enter key after each code you put in.
netsh winsock reset
- Finally, once all the codes executed, “Restart” your Windows computer.
So, that’s all you need to do to fix DNS PROBE FINISHED BAD CONFIG in your Chrome browser.
The DNS (Domain Name System) is a protocol that helps your system understanding domain names in terms of IP addresses. It’s a vital element to communicate with your computer when it comes to online activity.
So, any kind of glitches in DNS server can impact a lot to our online tasks.
I believe the solutions are easy to execute. I expect your feedback (Positive/Negative) as well.