The DNS_PROBE_FINISHED_BAD_CONFIG Error or DNS PROBE FINISHED BAD CONFIG Error is a very common error that users have to face when browsing in the Google Chrome web browser.
This is what the error looks like
This webpage is not available
The server at www.google.com can’t be found, because the DNS lookup failed. DNS is the network service that translates a website’s name to its Internet address. This error is most often caused by having no connection to the Internet or a misconfigured network. It can also be caused by an unresponsive DNS server or a firewall preventing Google Chrome from accessing the network.
Check your DNS settings
Contact your network administrator if you’re not sure what this means.
Try disabling network prediction
Go to the Chrome menu > Settings > Show advanced settings… and deselect “Predict network actions to improve page load performance”. If this does not resolve the issue, we recommend selecting this option again for improved performance.
Allow Chrome to access the network in your firewall or antivirus settings.
If it is already listed as a program allowed to access the network, try removing it from the list and adding it again.
Error Code: DNS_PROBE_FINISHED_BAD_CONFIG
A lot of people get this error, and when people come across this error, they go to Google some other way and search for solutions. In this post, we are going to give you 6 simple methods to solve the dns_probe_finished_bad_config error.
6 Methods To Fix DNS_PROBE_FINISHED_BAD_CONFIG Error in Chrome
Thoroughly check your internet connection
Most of the times the errors that are shown in Google Chrome arises due to problems in the internet connection to the device. These include faulty Ethernet cables, loose connections, faulty power cables, incorrect passwords, messed up configuration settings. Try restarting routers, replugging the cables. If you have no idea how to do that, contact the person who set up the system in the first place.
This is the reason and solution for dns_probe_finished_bad_config error in 90 percent of the cases. If you see internet working in other applications or devices, go to next method.
Go through your firewall or antivirus settings
The firewall or antivirus software frequently interfere with the working of browsers in order to secure the data of the user. This can create the DNS probe finished bad config error. Open your firewall software if any, and give a rule allow google chrome to access the internet. For antiviruses, see if there are any relevant settings in the internet security part of your antivirus suite.
Release/Renew IP Address using Command Prompt
If you do not know what command prompt already is, it is like the terminal you see in Linux. One uses commands on the Command Prompt (CMD) to communicate to the OS on a basic level. CMD is used to do several tasks.
One solution to the dns_probe_finished_bad_config error is to release and renew the IP address.
- To do this start by opening an elevated Command Prompt also known as Command Prompt with Admin Rights. Right-click on the bottom left corner to open the WinX menu and choose Command Prompt (Admin). You can also press the Windows Key + X.
- Once a black screen opens up, type in ” ipconfig /release ” and press enter. The process will take some time.
- Now type in ” ipconfig /renew ” and press enter.
- Close the command prompt and open the browser. See if that fixed the problem.
Flush the DNS using Command Prompt
This is the second thing you could do using the command prompt to solve the DNS probe finished bad config error. If the problem is with a bad DNS cache, flushing it will solve the dns_probe_finished_bad_config error.
- Open the elevated command prompt again.
- Type the following command and press enter
The DNS cache will now get flushed. Close the command window and open Google Chrome. Check if the problem still persists. if yes, try the fifth method.[Note- You could also use the command “netsh winsock reset catalog” to do this]
Change DNS Server Settings To Use Google DNS
Google provides a useful DNS server. Connecting to this will solve most of the DNS related issues in your PC. It can easily solve the dns_probe_finished_bad_config error.
- Start by opening the Network and Sharing Center. For this, right-click on the network icon and click on Open Network and Sharing Center. It can also be accessed from the control panel.
- Now Click on Change Adapter Settings from the Left pane. This will Open up a window called Network Connections.
- Right click on your internet connection and choose properties.
- Now Select the Internet Protocol Version 4 (TCP/IPv4) and click on Properties button.
- In the window that opens up, click on the radio button that says “Use the following DNS server addresses”.
- Set Preferred DNS Server as: 220.127.116.11
Set Alternate DNS Server as : 18.104.22.168
These are the IP addresses of the Google DNS.
- Tick the check box that says ‘Validate settings upon exit’.
- Click on Ok.
Close the window and check if the problem is resolved by opening a google chrome window.
Note: You can use the following IP addresses of OpenDNS if Google DNS does not work:
Preferred DNS server: 22.214.171.124
Alternate DNS server: 126.96.36.199
Update the router driver
The dns_probe_finished_bad_config error in chrome is sometimes caused by the outdated device driver of your router. Drivers are software that helps hardware devices to communicate with your computer. In order to update the device driver software and solve the DNS bad config error, follow the following steps. You should have a working internet connection for this. [Use USB tether or Wifi]
- Open Device Manager tool. Run “devmgmt.msc” on the RUN tool to get this.
- In the tree find and expand “Network Adapters“.
- Right-click on the network adapter that you use and click on Update Driver Software.
- Get the driver from the internet or choose it from your local files.
- Choose your compatible network hardware and continue by clicking on Next.
- The driver will now be updated.
- Reboot your router.
The DNS probe finished bad config error should be fixed by now.
End of the line
So here we have illustrated 6 possible methods to fix the popular DNS_PROBE_FINISHED_BAD_CONFIG error that is shown by the Google Chrome Browser. Do comment below your queries and we will try our best to help you.
Keep visiting and supporting PSnama 😉 <3
- 0.1 6 Methods To Fix DNS_PROBE_FINISHED_BAD_CONFIG Error in Chrome
- 1 End of the line