DNS Error: Sites Won't Load but Internet Works

What a DNS Error Means

A DNS (Domain Name System) error occurs when your computer or device cannot convert a user-friendly domain name (such as fixpedia.ru) into the numerical IP address where the server is located. Your browser displays messages like:

• DNS_PROBE_FINISHED_NXDOMAIN
• ERR_NAME_NOT_RESOLVED
• DNS server not responding
• Could not find server's IP address

Essentially, it's as if you were trying to call a friend, but your phone couldn't find their number in the phonebook. Your internet connection may still be working (for example, you could ping IP addresses directly).

Common Causes

1. Issues with your internet service provider (ISP). Their DNS servers may be overloaded, temporarily unavailable, or experiencing technical failures.
2. Incorrect DNS settings on your device. Settings automatically obtained from your ISP may be outdated or contain errors.
3. Corrupted local DNS cache. Your system or browser stores old, outdated domain records.
4. Blocking at the ISP or network level. Some ISPs or corporate networks block access to specific sites via DNS.
5. Malicious software. Trojans and viruses often change DNS servers in your system to their own to redirect traffic.
6. Corrupted or misconfigured hosts file. This local file can redirect domain names to incorrect IP addresses.
7. Windows network stack (Winsock) corruption. Damaged Winsock libraries can disrupt network requests, including DNS.

Solutions

Method 1: Quick Fix (Reboot and Flush Cache)

This is the first and simplest step, which resolves most temporary glitches.

1. Reboot your router and computer. Unplug the router's power cord for 30 seconds, then plug it back in. After the router has fully rebooted, restart your computer. This will clear all external and internal caches.
2. Flush the system DNS cache:
   • Windows: Open Command Prompt or PowerShell as an administrator. Enter the command:

     ipconfig /flushdns
     

     You will see the message Successfully flushed the DNS resolution cache.
   • macOS: Open Terminal. Enter the command (requires administrator password):

     sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
     

   • Linux (systemd-resolved):

     sudo systemd-resolve --flush-caches
     

     Or for older systems (nscd):

     sudo /etc/init.d/nscd restart
     

3. Clear the DNS cache in your browser. In your browser settings (Chrome, Firefox, Edge), find "History" or "Privacy" and select "Clear cache" or "Clear browsing data." Sometimes using incognito mode provides a quick check.

⚠️ Important: If the problem persists after rebooting the router, the issue may be on your ISP's side. Wait 10-15 minutes and try again.

Method 2: Switch to Public DNS Servers

A workaround that bypasses your ISP's DNS. Use reliable public DNS servers.

1. Choose DNS servers:
   • Cloudflare: 1.1.1.1 and 1.0.0.1 (fast, privacy-focused).
   • Google: 8.8.8.8 and 8.8.4.4 (stable, global).
   • Yandex (for Russia): 77.88.8.8 and 77.88.8.1 (optimized for local resources).
2. Configure DNS in your operating system:
   • Windows 10/11: Control Panel → Network and Internet → Network and Sharing Center → Change adapter settings. Right-click your active connection → Properties → select Internet Protocol Version 4 (TCP/IPv4) → Properties. Choose Use the following DNS server addresses and enter your chosen addresses. Uncheck Obtain DNS server address automatically.
   • macOS: System Preferences → Network → select your active interface (Wi-Fi/Ethernet) → Advanced → DNS tab. Click + and add the addresses. Remove the old servers from the list.
   • Linux (Ubuntu/GNOME): Settings → Network → click the gear icon for your connection → IPv4 or IPv6 tab. Under DNS, select Manual and add addresses, comma-separated.
   • Android: Settings → Network & Internet → Internet → tap your current network → Modify network → Advanced options → IP settings → Static (or leave DHCP but enter DNS addresses in the field). On some firmware, DNS is configured separately under Settings → Advanced → DNS.
   • iOS: Settings → Wi-Fi → tap the i next to your network → under DNS, select Manual and add the servers.
3. Save your settings and reconnect to the network. Try accessing the problematic site.

Method 3: Network Stack Reset (Windows)

If changing DNS didn't help, a Windows system component (Winsock) might be corrupted.

1. Perform a Winsock and TCP/IP reset. In Command Prompt (Administrator), enter these commands sequentially:

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

   Press Enter after each. The release command may temporarily disconnect you.
2. Restart your computer. Changes take effect only after a reboot.
3. Test. Try loading websites.

Method 4: Check hosts File and Antivirus

Local overrides or security software can block DNS resolution.

1. Check the hosts file:
   • Windows: Open the file C:\Windows\System32\drivers\etc\hosts in Notepad as an administrator.
   • macOS/Linux: Open a terminal and type sudo nano /etc/hosts (or open in any editor with sudo).
   • What to look for: Lines where a domain that won't load (or *, 0.0.0.0) is mapped to IP 127.0.0.1 or 0.0.0.0. For example:

     0.0.0.0   youtube.com
     127.0.0.1   facebook.com
     

     If you find such lines, comment them out by adding # at the start or delete them. Save the file.
2. Temporarily disable your antivirus/firewall. Some programs (especially "internet suites" or parental control software) can intercept DNS queries. Disable them for 5 minutes and check if the site works. If it does, configure exclusions in the software.

Method 5: Test with nslookup and ping

Find out where the chain breaks.

1. Open Command Prompt/Terminal.
2. Check resolution using your DNS:

   nslookup fixpedia.ru
   

   Or specify a particular DNS server you configured:

   nslookup fixpedia.ru 1.1.1.1
   

   If you see Non-existent domain or Server failed — the problem is with the DNS server or a block.If you see a correct IP address — your DNS server works; the issue may be in routing or on the website's side.
3. Try pinging the IP address you got from nslookup:

   ping 185.206.119.123  # (example IP for fixpedia.ru)
   

   If ping works (you get replies) but the site doesn't load by name — the problem is 100% in DNS on your device or between you and the DNS server.If ping fails (Request timed out), the problem is deeper — in routing or on the target server.

Prevention

• Use stable public DNS servers (Cloudflare, Google, Yandex) instead of your ISP's automatic ones. This avoids many external issues.
• Regularly clear the DNS cache (once a month) or after changing network settings.
• Monitor the integrity of your hosts file. Do not download or run suspicious "optimizers" or "ad blockers" that might modify it.
• Update your network card drivers and router firmware from the manufacturer's official website.
• Install antivirus with "web filtering" from reputable vendors to avoid hidden DNS redirection by attackers.