Fix DNS Problems

DNS (Domain Name System) translates website names like google.com into IP addresses. When DNS fails, you might see errors such as “Server not responding” or “DNS_PROBE_FINISHED_BAD_CONFIG.” This guide helps you reset your DNS settings and test resolution.

Tip: If you can reach websites by IP (e.g., ping 8.8.8.8) but not by name, the problem is almost certainly DNS-related.

Quick Fix Commands (Windows)

Run these commands in an Administrator Command Prompt to reset and refresh DNS:

Warning: Flushing DNS clears cached website addresses. You may experience slightly slower site loading immediately after the reset while DNS records repopulate.

ipconfig /flushdns
ipconfig /registerdns
nslookup google.com

Success Tip: A successful response to nslookup google.com confirms DNS resolution is functioning correctly.

Change DNS Servers

Switching to a reliable public DNS service can improve speed and reliability:

Google DNS: 8.8.8.8 and 8.8.4.4
Cloudflare DNS: 1.1.1.1 and 1.0.0.1
OpenDNS: 208.67.222.222 and 208.67.220.220

Warning: Only change DNS settings if you have administrator rights. Incorrect entries can result in complete loss of internet connectivity.

Windows: Go to Settings → Network & Internet → Adapter Properties → Internet Protocol Version 4 (TCP/IPv4) → Select “Use the following DNS server addresses.”

Verify DNS Function

Use these commands to confirm whether DNS or connectivity is the issue:

nslookup microsoft.com
ping 8.8.8.8

If ping 8.8.8.8 works but nslookup fails, DNS is not resolving.
If both fail, the issue may be your network adapter or router.

Success Tip: Once fixed, flush DNS again and restart your browser to apply new settings immediately.

Back to Network Guides