In this tutorial, you will learn how to fix DNS_PROBE_FINISHED_BAD_CONFIG in chrome or DNS PROBE FINISHED BAD CONFIG in Google Chrome, this occurs due to some problems in DNS or misconfigured network settings.
If you are getting “This webpage is not available” with the error code “DNS_PROBE_FINISHED_BAD_CONFIG” while accessing websites in Google Chrome this article will guide you to fix it. Before going further Restart your internet router and try to open websites it may fix the problem. If you are continuously getting DNS_PROBE_FINISHED_BAD_CONFIG in Chrome follow this tutorial to fix it.
How to fix DNS_PROBE_FINISHED_BAD_CONFIG in Chrome
Here are the Two methods to solve this problem.
- Using Command Prompt(CMD)
- Change DNS Server Settings
Method#1 Using Command Prompt(CMD) to fix DNS_PROBE_FINISHED_BAD_CONFIG in Chrome
Step#1 Start Command Prompt(CMD) as an Administrator.
Step#2 Now Run the following Commands one at a time:
netsh int ip set dns
netsh winsock reset
Restart your Computer to fix DNS_PROBE_FINISHED_BAD_CONFIG in chrome.
Method#2 Change DNS Server Settings to fix DNS_PROBE_FINISHED_BAD_CONFIG in Chrome
Step#1 Choose Open Network and Sharing Center by right-clicking on the Network icon.
Step#2 Choose Change adapter settings at the top left or Click on the Connections Wi-Fi().
Step#3 Choose Properties
Step#4 Select Internet Protocol Version 4 (TCP /IPv4) and click on its Properties.
Step#5 Select Use the following DNS server addresses, and type the following:
Preferred DNS server 8 8 8 8
Alternate DNS server 8 8 4 4
That is it now you can fix DNS PROBE FINISHED BAD CONFIG error in Chrome.
Related to this Post:
- Fixed: ERR_SPDY_PROTOCOL_ERROR in Chrome
- DNS_PROBE_FINISHED_NXDOMAIN in Chrome
- Fixed: ERR_NAME_RESOLUTION_FAILED
- Fixed: ERR_NETWORK_CHANGED in Chrome
- Fixed: DNS Lookup Failed Error in Chrome