DNS not responding?
Describe your symptoms. Get a likely-cause diagnosis, a top-down diagnostic ladder, OS-specific commands, and fix-by-cause instructions.
About "DNS server not responding"
"DNS server not responding" almost never means the DNS server is actually broken. The real culprit is usually: stale local cache, wrong DNS configured in the router, a hosts file override from years ago, a VPN intercepting queries, or — most commonly — the user just lost connectivity entirely and DNS is the messenger getting shot.
The Qaynaq Labs DNS troubleshooter walks down a diagnostic ladder, quickest checks first, most invasive last. OS-specific commands for Windows, macOS, Linux, Android, and iOS. If you've tried everything and the issue persists, the "when to call your ISP" section flags the scenarios where it's actually their problem to fix.
Frequently asked
Should I just switch to 1.1.1.1 or 8.8.8.8?
Sometimes — but first confirm DNS is actually the problem. Switching DNS won't help if your router has an issue routing port 53. The diagnostic ladder tests this in step 1-2.
Does using public DNS leak my browsing to Cloudflare/Google?
They see which domains you visit, just like your ISP does. Cloudflare publishes a no-logs policy; Google retains for 24-48 hours. For maximum privacy use DNS-over-HTTPS with a privacy-focused provider.
Why does the error sometimes resolve itself?
Local caches expire, your router renegotiates DHCP, or the original DNS server comes back online. Doesn't mean nothing was wrong — means whatever was transient passed.
How do I flush DNS cache?
Each OS has its own command (included in fixes section). Windows: <code>ipconfig /flushdns</code>. macOS: <code>sudo dscacheutil -flushcache</code>. Linux varies by distro (systemd-resolve or systemctl restart systemd-resolved).