DNS server is not responding (DNS_PROBE_FINISHED_BAD_CONFIG)
The operating system cannot translate domain names into IP addresses because the assigned DNS server is unreachable or timing out.
Internal desktop parts run on harmless 12V DC voltage and cannot shock you. Simply unplug the wall power cable first, then touch the unpainted metal case frame to ground static electricity.
Common Symptoms & Tells
- Web browser shows error 'DNS_PROBE_FINISHED_NXDOMAIN' or 'Server IP could not be found'
- Pinging numeric IPs (e.g., 'ping 1.1.1.1') works, but pinging domain names ('ping google.com') fails
- Chat apps like Discord stay connected while browser websites refuse to load
Interactive Fix Checklist
0 of 4 steps completedSwitch to public secure DNS servers
Open Settings → Network & Internet → select your adapter → DNS server assignment → Edit → Manual → IPv4 On. Preferred DNS: 1.1.1.1, Alternate DNS: 1.0.0.1 (Cloudflare) or 8.8.8.8 (Google).
Clear the local Windows DNS cache
Open Command Prompt as admin and execute 'ipconfig /flushdns'. Verify message 'Successfully flushed the DNS Resolver Cache'.
Restart the DNS Client service
Run 'net stop dnscache' and 'net start dnscache' in Command Prompt, or reboot the PC.
Disable third-party VPN and DNS blockers
Ad-blocking software (AdGuard, Pi-hole) or stale VPN configurations redirect DNS traffic to dead local loopback addresses.
Still having trouble with your PC?
Describe what is happening to your AI Technician. We will tailor the fix to your exact hardware setup.