How to Fix 'DNS Probe Finished Bad Config' Warnings

The "DNS Probe Finished Bad Config" error occurs when your web browser cannot resolve a website's domain name because your local machine's network configuration or DNS settings are misconfigured. This frustrating connection issue stops traffic in its tracks, but it can usually be resolved by resetting your local DNS cache, changing your nameserver addresses, or releasing your IP configuration.

Diagnosing network connectivity issues can be tricky without the right utilities, which is why utilizing a tool like the NS Lookup tool on XiaTools helps you test domain name resolution directly against authoritative name servers to verify if the issue is local or global.

Understanding the DNS Probe Error

When you type a URL into your browser, your operating system queries a Domain Name System (DNS) server to translate the human-readable hostname (like example.com) into a machine-readable IP address (like 192.0.2.1). If your local network configuration, TCP/IP stack, or router encounters a corrupt configuration state, the DNS probe fails, returning the bad config error.

Common Symptoms and Causes

• Symptoms: Browser displays "DNS_PROBE_FINISHED_BAD_CONFIG" in Google Chrome, Microsoft Edge, or Brave, while other applications fail to connect to the internet.
• Causes: Corrupted DNS resolver cache, misconfigured static IP addresses, VPN or proxy software interference, or faulty router firmware.

---

Step-by-Step Fixes for Windows

If you are running Windows 10 or Windows 11, follow these systematic steps to clear out corrupted network configurations.

Step 1: Flush the DNS Cache and Renew IP Configuration

Open Command Prompt as an administrator by typing cmd in the Windows search bar, right-clicking Command Prompt, and selecting Run as administrator. Execute the following commands sequentially:

ipconfig /flushdns
ipconfig /release
ipconfig /renew
netsh int ip reset
netsh winsock reset

Restart your computer after running these commands to ensure the TCP/IP stack reinitializes cleanly.

Step 2: Change Your DNS Server Addresses

Often, Internet Service Provider (ISP) DNS servers experience outages or configuration hiccups. Switching to a public DNS provider like Cloudflare (1.1.1.1) or Google (8.8.8.8) fixes the bad config warning immediately.

1. Open the Settings app and go to Network & Internet > Status (or Network & Status).
2. Click on Change adapter options (or Advanced network settings > More adapter options).
3. Right-click your active connection (Ethernet or Wi-Fi) and select Properties.
4. Double-click on Internet Protocol Version 4 (TCP/IPv4).
5. Select Use the following DNS server addresses and enter:
   • Preferred DNS server: 1.1.1.1
   • Alternative DNS server: 1.0.0.1
6. Click OK and restart your browser.

---

Step-by-Step Fixes for macOS

Mac users can encounter similar DNS resolution roadblocks. Here is how to clear them out on macOS.

Step 1: Flush the macOS DNS Cache

Open the Terminal app via Spotlight or by navigating to Applications > Utilities > Terminal. Enter the command corresponding to your macOS version:

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

Enter your Mac administrator password when prompted. Note that characters will not appear on the screen as you type for security reasons.

Step 2: Update DNS Servers on Mac

1. Open System Settings (or System Preferences).
2. Click on Network in the sidebar.
3. Select your active network connection (Wi-Fi or Ethernet) and click Details.
4. Click on the DNS tab.
5. Click the + button under the DNS Servers list and add 8.8.8.8 and 1.1.1.1.
6. Click OK and then Apply.

---

Verifying DNS Resolution via Command Line

Once you have applied troubleshooting steps, verify that your machine can successfully resolve hostnames using command-line diagnostic utilities.

Using nslookup

Run a manual query against a specific domain to ensure your local resolver is working properly:

nslookup example.com

Sample Output:

Server:		1.1.1.1
Address:	1.1.1.1#53

Non-authoritative answer:
Name:	example.com
Address: 192.0.2.1

Using dig (macOS and Linux)

dig example.com +short

Sample Output:

192.0.2.1

Troubleshooting Tool	Primary Function	Best Used For
ipconfig /flushdns	Clears local OS DNS cache	Fixing outdated record pointers on Windows
nslookup	Queries DNS servers for records	Verifying if domain name resolves correctly
ping	Tests end-to-end IP connectivity	Checking if a host is reachable online
tracemonter / tracert	Maps network packet path	Identifying routing bottlenecks or failures

---

Advanced Troubleshooting

If basic fixes fail, examine deeper system configurations that might override your network settings.

Check for VPN and Proxy Interference

Virtual Private Networks (VPNs) and third-party proxy tools manipulate your operating system's routing tables and DNS configurations. If your VPN client crashes or disconnects improperly, it can leave behind bad network configurations.

1. Temporarily disable or completely uninstall any third-party VPN or security suite software.
2. Verify your browser proxy settings:
   • In Windows, open Internet Options via the Control Panel, go to the Connections tab, click LAN settings, and ensure "Use a automatic configuration script" or proxy server checkboxes are unchecked unless required by your network.

Inspect the Local Hosts File

If a specific website fails to load and throws a configuration error, check your local hosts file to ensure the domain is not hardcoded to an incorrect IP address (such as 192.0.2.5 or 127.0.0.1).

• Windows path: C:\Windows\System32\drivers\etc\hosts
• macOS/Linux path: /etc/hosts

Open the file in a text editor with administrator privileges. Ensure there are no lingering custom entries mapping your target domain to the wrong IP address.

---

Quick Troubleshooting Checklist

• Flushed the local DNS resolver cache (ipconfig /flushdns or dscacheutil).
• Released and renewed the local IP address lease.
• Switched to public DNS resolvers like Cloudflare (1.1.1.1) or Google (8.8.8.8).
• Disabled active VPN clients, browser extensions, or proxy servers.
• Restarted both the computer and local network router/modem.
• Tested domain resolution using online diagnostic tools.