DNS not resolving not working means your device cannot translate domain names into IP addresses, blocking internet access. In 2026, this issue stems from misconfigured DNS servers, ISP outages, firewall rules, or corrupted cache. The fix usually involves flushing DNS cache, switching to public DNS servers like Cloudflare (1.1.1.1), or checking your router configuration.
DNS resolution failures affect an estimated 8-12% of internet users monthly, according to Cloudflare’s 2025 connectivity report. When DNS fails, websites become unreachable even though your network connection remains active. This creates confusion because other internet services may still function while browsers display “server not found” errors. Understanding DNS troubleshooting saves hours of downtime and prevents unnecessary ISP support calls.
DNS (Domain Name System) acts as the internet’s phone book, converting human-readable domains like abdulabror.com into IP addresses like 104.21.68.234. When you type a URL, your device queries DNS servers in this sequence:
A failure at any stage causes “DNS not resolving” errors. Modern DNS infrastructure in 2026 uses DNS-over-HTTPS (DoH) and DNS-over-TLS (DoT) for encrypted queries, but these protocols can introduce new failure points when misconfigured.
The most common causes break down into five categories:
Server-side issues: Your configured DNS servers may be offline, overloaded, or blocking requests. ISP DNS servers experience outages during network maintenance or cyberattacks. In March 2026, a distributed denial-of-service attack took down multiple regional ISP DNS services across Southeast Asia for six hours.
Local cache corruption: Operating systems cache DNS responses to speed up browsing. When cache entries become stale or corrupted, they return incorrect or outdated IP addresses. This frequently happens after network changes or malware infections.
Firewall and security software: Overly aggressive firewall rules, VPN configurations, or antivirus programs can block UDP port 53 (traditional DNS) or TCP port 853 (DNS-over-TLS). Enterprise security tools sometimes whitelist only specific DNS servers.
Router configuration errors: Incorrect DNS settings in your router propagate to all connected devices. Firmware bugs or failed DHCP configurations leave devices without valid DNS server addresses.
Network layer problems: IPv6 misconfigurations, MTU size mismatches, or routing issues can prevent DNS packets from reaching their destination even when other traffic flows normally.
Start with these command-line diagnostics to isolate the failure point:
# Test DNS resolution with nslookup
nslookup abdulabror.com
# Query a specific DNS server directly
nslookup abdulabror.com 1.1.1.1
# Trace DNS resolution path (Windows)
nslookup -debug abdulabror.com
# Check DNS with dig (Linux/macOS)
dig abdulabror.com +trace
If nslookup against 1.1.1.1 (Cloudflare) or 8.8.8.8 (Google) succeeds but your default DNS fails, the problem lies with your configured DNS servers. If all queries fail, check network connectivity with ping 1.1.1.1 to verify basic IP routing works.
Browser developer tools (F12) provide additional clues. The Network tab shows whether failures occur during DNS lookup (gray bars) or after connection establishment (red bars). Chrome’s chrome://net-internals/#dns page displays cached DNS entries and query logs.
Public DNS resolvers offer better reliability and performance than most ISP defaults. According to DNSPerf’s January 2026 benchmarks, these providers lead in global response times:
Cloudflare (1.1.1.1, 1.0.0.1): Fastest average response time at 10.3ms globally. Privacy-focused with no query logging. Supports DoH and DoT protocols. Best for general use and privacy-conscious users.
Google Public DNS (8.8.8.8, 8.8.4.4): 13.7ms average response time with extensive geographic coverage. Integrates with Google Safe Browsing for malware protection. Ideal for enterprise environments needing broad compatibility.
Quad9 (9.9.9.9): 15.2ms response time with built-in threat blocking. Non-profit operation with strong privacy commitments. Recommended for security-focused deployments.
To change DNS servers on Windows 11:
1. Open Settings > Network & Internet
2. Click your connection (Wi-Fi or Ethernet)
3. Click "Edit" next to DNS server assignment
4. Select Manual, enable IPv4
5. Enter Preferred DNS: 1.1.1.1
6. Enter Alternate DNS: 1.0.0.1
7. Click Save
Flushing DNS cache removes corrupted entries and forces fresh queries. The commands vary by operating system:
# Windows (run as Administrator)
ipconfig /flushdns
ipconfig /registerdns
# macOS
sudo dscacheutil -flushcache
sudo killall -HUP mDNSResponder
# Linux (systemd-resolved)
sudo systemd-resolve --flush-caches
# Linux (nscd)
sudo /etc/init.d/nscd restart
Clear browser DNS cache separately in Chrome by visiting chrome://net-internals/#dns and clicking “Clear host cache.” Firefox users should type about:networking#dns and click “Clear DNS Cache.”
Router cache requires a full router reboot or accessing the admin panel to clear DNS records. This step is crucial because cached entries on your router affect all connected devices simultaneously.
Traditional DNS queries transmit in plaintext, allowing ISPs and network administrators to monitor browsing activity. DNS-over-HTTPS (DoH) and DNS-over-TLS (DoT) encrypt queries, preventing surveillance while maintaining functionality.
Mozilla Firefox enables DoH by default in supported regions, routing queries through Cloudflare or NextDNS. Chrome and Edge offer DoH as an opt-in feature under privacy settings. According to the Internet Society’s 2025 encryption report, 34% of global DNS traffic now uses encrypted protocols, up from 18% in 2024.
Configure DoH manually on systems without native support using DNS proxy software like dnscrypt-proxy or cloudflared. Enterprise networks should evaluate whether encrypted DNS bypasses content filtering policies before deployment.
Your devices likely use different DNS servers. Phones often use mobile carrier DNS or hard-coded DoH providers, while computers inherit settings from your router. Check each device’s network configuration separately and ensure they point to the same reliable DNS servers.
Yes. VPNs route DNS queries through their own servers, and connection issues or DNS leaks create resolution failures. Check your VPN’s DNS settings and test with the VPN disconnected. Some VPN protocols like WireGuard require explicit DNS server configuration that breaks when misconfigured.
DNS records include a Time-To-Live (TTL) value ranging from 60 seconds to 24 hours. Your operating system respects these TTLs when caching. Browsers maintain separate caches with their own TTLs. Flushing cache forces immediate re-queries regardless of TTL.
A timeout occurs when DNS servers don’t respond within the configured wait period (usually 5-10 seconds), often indicating network connectivity problems. A failure returns an error response like “NXDOMAIN” (domain doesn’t exist) or “SERVFAIL” (server error), showing the DNS server received your query but couldn’t resolve it.
Most routers act as DNS forwarders, not resolvers. They cache queries but forward requests to upstream servers. Using your router’s IP as DNS adds an extra hop and potential failure point. Configure devices to use public DNS servers directly for better reliability and performance.