DNS_PROBE_FINISHED_BAD_CONFIG
DNS_PROBE_FINISHED_BAD_CONFIG Error
What This Error Means
The DNS_PROBE_FINISHED_BAD_CONFIG error indicates that the browser was unable to resolve the domain name because of a misconfiguration in the local network's DNS settings. Unlike NXDOMAIN (which means the domain doesn't exist), this error means the DNS server itself is unreachable, invalid, or refusing to answer.
Common Causes
- Manually configured DNS server IP addresses are incorrect or offline.
- Router DNS settings are corrupted or blocking requests.
- Firewall or antivirus software blocking DNS traffic (port 53).
- VPN software failed to reset DNS settings after disconnecting.
- Third-party DNS filtering software (like parental controls) malfunctioning.
How to Fix It (For Users)
- 1 Flush your DNS cache using `ipconfig /flushdns` (Windows) or `sudo killall -HUP mDNSResponder` (macOS).
- 2 Change your network adapter settings to obtain DNS server addresses automatically (DHCP).
- 3 Switch to a reliable public DNS provider like Google (8.8.8.8) or Cloudflare (1.1.1.1).
- 4 Restart your router and modem to reset local network configurations.
- 5 Disable any active VPNs or proxy servers temporarily.
For Site Owners / Developers
- This is a client-side connectivity issue. Ensure your domain's DNS records are propagating correctly globally to rule out server-side issues.
- Advise users to check their local network settings.
When It Is NOT Your Fault
If your ISP's default DNS servers are experiencing an outage.
Check if this outage affects everyone globally
This error often indicates a wider problem. Use our tool to verify if the site is down for everyone.
Check Website Status →Recommended Tool to Prevent This Error
Ensure your server is always online and fast with high-performance cloud hosting.