Are you frequently getting disconnected from Internet? Do you have to frequently use Refresh button to reload webpages? Do you have to frequently turn off and then turn on WiFi to get connected to internet? Finally, do you get this error message on your chrome browser frequently?
<website name> server DNS address could not be found.Try:
- Checking the proxy, firewall, and DNS configuration
- Running Windows Network Diagnostics
Cause for DNS _PROBE _FINISHED _BAD _CONFIG Error Message
DNS server allow a web browser to convert a website name to IP address and IP address to website. Every website got their own unique IP address. Machines like to communicate with each other using these numbers. Since it is impossible for humans to remember the IP address for websites, these numbers need to be converted to names which can be remembered easily.
For e.g., from the error message in the picture, the chrome browser in my computer is not able to contact atechjourney website. When I searched for atechjourney in chrome, the browser immediately contact DNS server to convert the name into IP address, so that it can connect to the IP address where the website is hosted. Since there is a problem with DNS, chrome is unable to convert the IP address which means no more communication is possible. That is when this error message is thrown out.
This can be
- Problem with computer
- Problem with ISP (Internet Service Provider)
If you have multiple devices that connect to WiFi, check if the other devices is able to connect internet without any problem. If all the devices have problems getting online using the same WiFi, this is a problem with ISP. Contact them.
How to fix frequent DNS_ PROBE_ FINISHED_ BAD_ CONFIG Error Message
Use Global DNS address
- Press Windows Key + R to open Run window.
- Type ncpa.cpl to open Network connections window which display all the connections including the one that you are connected now.
- Click Properties
- Click Internet Protocol Version 4. Then click Properties again
- In General Tab, select the option Use the following DNS server addresses
- Use Preferred DNS server as 184.108.40.206 and Alternate DNS server as 220.127.116.11
- Click OK
Check if the problem is solved. Usually the above step does not need a computer restart. But if the problem is not resolved, it is worth shutting down the computer and the router/modem. Keep it turned off for a minute, then turn it on. Check if the problem is fixed.
Reset IP and winsock using command prompt
- Open command prompt with Admin rights (In Windows 10, right click Start button -> select Command Prompt (Admin))
- Type the commands in the following order
netsh int ip reset c:\resetlog.txt
netsh winsock reset
- Restart computer
Check if the problem is solved.
Restart your device and WiFi/modem. Assuming that you may have kept the WiFi/modem or device turned on for longer periods, this step is recommended.
Turn off all the devices for a minute and then turn it on. Check if the problem is fixed.
Restart DNS client
As a tech support professional, I rarely had this step fixing this problem. But it is worth trying considering it did fix a couple of case
- Press Windows Key + R to open Run window
- Type services.msc to open Services window
- Right click on DNS client. Click restart. If the service is stopped, start the service
Check the problem status.
Recheck Security Software and Firewall settings
Since all the steps failed till now, try this last step. It is possible that a software or some App is blocking your browser from properly communicating with DNS. This can happen when the security software or firewall settings change automatically either because of a failed update or attack from malware.
Re-configure your security software and firewall properly. Try to reset all settings to default which should fix the problem. But at times, even resetting software may not work if the software is damaged beyond repair or out of expiry. Uninstall the security software or firewall and check if the problem is fixed.
Also, make sure there are no browser add-ons or extensions which is accidentally blocking DNS access.
If none of the step worked to fix the problem, it is time to contact your ISP and check if the problem is from their end.