This error message means that the system responsible for translating a human-friendly web address (like vvdryvat.top) into a computer-friendly IP address (like 123.45.67.89) has failed. Your browser, in short, lost its “phonebook” and cannot find the number for the website you’re trying to call.

Key Takeaways

  • The Core Problem: The “DNS Server Not Responding” error means the “internet’s phonebook” (the Domain Name System) is inaccessible. Your device cannot find the IP address for the website you want to visit.
  • Most Common Fixes: For most users, the two most effective solutions are restarting the router (Method 2) and changing the DNS server to a public one like Google’s 8.8.8.8 or Cloudflare’s 1.1.1.1 (Method 6).
  • Troubleshooting is Layered: The problem can be on your device (bad cache), your router (needs a restart), your ISP (server is down), or even the website itself (bad configuration). Our methods will help you test each layer.
  • It’s Fixable: While frustrating, this error is almost always solvable with the right troubleshooting steps. This guide will walk you through them, from the simplest restart to more advanced network configurations.

What is DNS, Really? (And Why Does It Fail?)

Before we dive into the fixes, it helps to understand exactly what’s broken. The Domain Name System (DNS) is a foundational technology of the internet. Here’s how it all fits together.

The Internet’s Phonebook

Think of the internet as a massive city. Every house and building (a website, a server) has a unique, logical address. This address is its IP Address (Internet Protocol address), which looks something like 172.217.14.228.

This system is great for computers, which love numbers, but terrible for humans. You would never remember that 172.217.14.228 is Google. Instead, you remember the human-friendly domain name: google.com.

The DNS is the massive, global “phonebook” that connects the name (google.com) to the number (172.217.14.228).

When you type google.com into your browser, a rapid, multi-step process called a DNS lookup happens in the background:

  1. Your browser asks your computer’s operating system (like Windows or macOS) if it knows the IP for google.com.
  2. If your computer doesn’t know, it asks your router.
  3. If your router doesn’t know, it passes the request to a DNS Resolver, which is a special server run by your ISP (like Comcast, AT&T, or Verizon).
  4. This resolver then goes and finds the correct IP address from the “authoritative” servers that manage the google.com domain.
  5. It passes this IP address back to your computer, which passes it to your browser.
  6. Your browser then connects directly to that IP address, and the website loads.

This entire process usually takes less than a second.

Why Does It Fail? The Common Culprits

The “DNS Server Not Responding” error means that this chain is broken. Your computer asked your router, which asked your ISP’s DNS server, and that server… never answered. Or it answered with, “I don’t know,” and the request failed.

This can happen for several reasons:

  • The DNS Server is Down: The server itself (usually your ISP’s) might be having technical problems, be overloaded, or be down for maintenance.
  • A Corrupt DNS Cache: Your computer and browser both keep a “cache,” or a short-term memory, of recent DNS lookups to speed things up. If this cache becomes outdated or corrupt, it can point you to the wrong place or a non-existent one.
  • Bad Network Configuration: Your device’s network settings might be pointing to the wrong DNS server address.
  • Firewall/Antivirus Interference: An over-aggressive security program can mistakenly block DNS requests, thinking they are a threat.
  • Outdated Drivers: Your computer’s network adapter drivers (the software that lets it talk to the network) might be buggy or corrupt.
  • The Website’s DNS is Broken: Sometimes, the problem isn’t with you at all. The website you’re trying to reach may have misconfigured its own DNS records.

Our 10 methods will work through this list, from the most likely and easiest-to-fix culprits to the more advanced ones.

Before the Fix: Run This 30-Second Diagnosis

Before you start changing settings, let’s narrow down the scope of the problem.

  • Is it Just This Website? Try to visit a few other, major websites. Can you get to google.com or bbc.com? If all other sites work, but one specific site fails, the problem is likely with that website’s DNS, not yours.
  • Is it Just This Device? Grab your smartphone. Turn off Wi-Fi so that it’s using its mobile data connection. Can you visit the website? If you can, the problem is somewhere in your local network (your Wi-Fi, your router, or your computer).
  • Is it Just This Browser? Try a different web browser. If the site fails in Chrome but works in Edge or Firefox, the problem is isolated to your primary browser.

If the error happens on all browsers, on all websites, and on all devices on your Wi-Fi network, the problem is almost certainly your router or your ISP’s DNS service. This diagnosis helps us focus on the most likely fixes.

10 Proven Methods to Fix the “DNS Server Not Responding” Error

Let’s go through the solutions one by one, starting with the simplest.

Method 1: Restart Your Computer

It’s the classic IT advice for a reason. Restarting your computer clears countless temporary files, flushes memory, and resets the operating system’s network stack. A simple reboot can solve a surprising number of “glitches” that may be holding onto a bad network configuration.

  • Why it works: It clears the system’s active memory and forces all applications and services, including networking services, to restart from a clean state.
  • How to do it: Don’t just close the lid of your laptop. Go to the Start Menu or Apple Menu and select Restart. This ensures a full and proper shutdown and startup cycle.

Method 2: Power Cycle Your Router and Modem

This is the single most effective solution for most home network problems. Your router is a small computer, and just like your laptop, it can get confused, overheat, or have its memory fill up with errors. Power cycling (a fancy term for turning it off and on again) clears its cache and forces it to establish a new, clean connection to your ISP.

  • Why it works: It flushes the router’s temporary memory (cache) and forces it to get a new IP address and fresh DNS server information from your ISP.
  • How to do it (The Right Way):
    1. Unplug the power cables from both your modem and your router. (If you have a combined modem/router unit, just unplug that one).
    2. Wait for at least 60 seconds. This is important. It ensures that all the capacitors in the devices fully discharge, clearing all volatile memory.
    3. Plug the power cable back into your modem first.
    4. Wait for 1-2 minutes until all the status lights (Online, Internet, etc.) are stable and green.
    5. Now, plug the power cable back into your router.
    6. Wait another 1-2 minutes for its lights to stabilize.
    7. Once your Wi-Fi network reappears, reconnect your computer and test.

Method 3: Switch Your Web Browser

If your 30-second diagnosis showed the problem was only in one browser, this is your fix. A browser’s cache or a faulty extension can be the source of the problem.

  • Why it works: This test isolates the problem. If the site loads in a different browser, you know your computer’s main network connection is fine and the problem is contained within the original browser.
  • How to fix the original browser:
    1. Clear the cache: Go into your browser’s settings (History > Clear browsing data) and clear everything, especially “Cached images and files”.
    2. Disable extensions: Go to your browser’s extensions menu (e.g., chrome://extensions in Chrome). Turn off all your extensions, especially ad blockers or security extensions. Restart the browser and see if it works. If it does, re-enable your extensions one by one until you find the one causing the problem.

Method 4: Clear Your Browser’s DNS Cache

Separate from your computer’s DNS cache (Method 5), modern browsers like Chrome keep their own internal DNS cache to speed things up. If this cache is corrupt, it can cause problems even if your operating system is fine.

  • Why it works: It forces the browser to re-request the IP address for a website instead of relying on its own, potentially outdated, saved copy.
  • How to do it in Google Chrome:
    1. Open a new tab in Chrome.
    2. In the address bar, type: chrome://net-internals/#dns
    3. Press Enter.
    4. You will see a “Host resolver cache” page. Click the Clear host cache button.
    5. Restart Chrome and test the website.
  • In other browsers (Firefox, Safari, Edge): This cache is typically cleared when you clear the main browser cache (Method 3).

Method 5: Flush Your Operating System’s DNS Cache

This is one of the most effective technical fixes. Your operating system (Windows or macOS) keeps a master list of recent DNS lookups. If an entry in this list is corrupt (e.g., it has the wrong IP for a website), it can lead to this error. Flushing the cache forces the computer to forget all its saved lookups and start fresh.

  • Why it works: It removes all saved DNS entries from your computer’s local cache, forcing it to ask the DNS server for a fresh, correct IP address for every website you visit.

How to Flush DNS on Windows 10/11

  1. Click the Start Menu and type cmd.
  2. You will see Command Prompt. Right-click on it and select Run as administrator.
  3. A black terminal window will open. Type the following command exactly and press Enter: ipconfig /flushdns
  4. You should see a message: “Successfully flushed the DNS Resolver Cache.”
  5. Now, type these two commands, pressing Enter after each one, to release and renew your IP address: ipconfig /release ipconfig /renew
  6. Close the Command Prompt and try visiting the website again.

How to Flush DNS on macOS

  1. Open Spotlight (Cmd + Space) and type Terminal. Press Enter.
  2. A terminal window will open. The command you need varies slightly by macOS version, but this one works for most modern versions (Ventura, Sonoma, Monterey, Big Sur): sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
  3. Type that command and press Enter.
  4. It will ask for your password. This is your normal Mac login password. You won’t see the cursor move as you type. This is normal.
  5. Press Enter. You should see a confirmation or it will just return to the prompt.
  6. Restart your browser and test.

Method 6: Switch to a Public DNS Server (The Most Common Fix)

If flushing the cache didn’t work, this is your next best bet. The “DNS Server Not Responding” error is often literal: your ISP’s default DNS server is slow, overloaded, or just plain down.

The solution is to manually tell your computer (or router) to stop using your ISP’s default servers and instead use a free, fast, and reliable public DNS server. The most popular ones are run by Google and Cloudflare.

  • Why it works: You are bypassing your ISP’s (potentially faulty) DNS system and using a high-performance, globally redundant system instead. This is often faster and more secure.

Popular Public DNS Servers

Here are the addresses you’ll need. We recommend using either Cloudflare or Google.

ProviderPrimary DNSSecondary DNSKey Features
Cloudflare1.1.1.11.0.0.1Excellent Speed & Privacy
Google8.8.8.88.8.4.4High Reliability & Security
OpenDNS208.67.222.222208.67.220.220Family-Friendly Filtering

How to Change DNS on Windows 10/11

  1. Press the Windows key + R to open the Run dialog.
  2. Type ncpa.cpl and press Enter. This opens the Network Connections window.
  3. Right-click on your active network connection (it will be “Wi-Fi” or “Ethernet”) and select Properties.
  4. In the list, find and click on Internet Protocol Version 4 (TCP/IPv4), then click the Properties button.
  5. Click the bubble next to Use the following DNS server addresses:
  6. In the “Preferred DNS server” box, type: 1.1.1.1 (for Cloudflare)
  7. In the “Alternate DNS server” box, type: 1.0.0.1
  8. Click OK, then Close.
  9. You should flush your DNS cache again (Method 5) for the change to take effect immediately.

How to Change DNS on macOS

  1. Click the Apple Menu in the top-left corner and go to System Settings…
  2. Click on Network in the sidebar.
  3. Click on your active connection (e.g., Wi-Fi).
  4. Click the Details… button.
  5. In the new window, click DNS in the sidebar.
  6. Under “DNS Servers,” click the + button.
  7. Type 1.1.1.1 and press Enter.
  8. Click the + button again and type 1.0.0.1.
  9. (If you see your old DNS server (often an address like 192.168.1.1), you can select it and click the – button to remove it, or just leave it. Your Mac will prioritize the ones you added.)
  10. Click OK, then Apply.
  11. You should flush your DNS cache (Method 5) for the change to take effect.

Method 7: Temporarily Disable Your Firewall and Antivirus

Your computer’s digital security guards (firewall and antivirus) can sometimes be too good at their jobs. They might mistakenly identify normal DNS traffic as suspicious and block it.

  • Why it works: This is a diagnostic step. By temporarily turning off these services, you can check if they are the source of the blockage.
  • How to do it:
    • Windows: Go to Settings > Privacy & security > Windows Security. Click on “Firewall & network protection” and temporarily turn off the firewall for your active network.
    • macOS: Go to System Settings > Network > Firewall and toggle it off.
    • Third-Party Antivirus (Norton, McAfee, etc.): Find the icon for your security software in your system tray or menu bar, right-click it, and look for an option like “Disable Protection” or “Disable Firewall” for a short time (e.g., “for 15 minutes”).

Important: This is only a test. After you test the website, turn your firewall and antivirus back on immediately, regardless of the result. If this did fix the problem, you need to go into your security software’s settings and find a way to “whitelist” your web browser or unblock network-level DNS queries.

Method 8: Disable Secondary Network Connections

Sometimes your computer gets confused about how to access the internet. If you have a VPN active, or you’re plugged into an Ethernet cable while also connected to Wi-Fi, your system might be trying to send DNS requests down the wrong pipe.

  • Why it works: It simplifies your computer’s connection, leaving it with only one clear, unambiguous path to the internet.
  • How to do it:
    • Disconnect from your VPN: If you are running a VPN, disconnect it completely and try again. VPNs route all your traffic through their own servers, and their DNS servers can sometimes fail.
    • Disable Wi-Fi: If you are plugged into an Ethernet cable, click the Wi-Fi icon and turn Wi-Fi off.
    • Unplug Ethernet: If you are primarily using Wi-Fi, make sure you don’t have an Ethernet cable also plugged in.

Method 9: Update Your Network Adapter Drivers (Windows)

The network adapter is the physical hardware (the Wi-Fi card or Ethernet port) that connects your computer to the network. The drivers are the software that tells the operating system how to use that hardware. If this software is old or corrupt, it can cause all kinds of network failures.

  • Why it works: An update can fix bugs or corruption in the driver software that is preventing your adapter from communicating correctly.
  • How to do it (Windows):
    1. Click the Start Menu and type Device Manager. Press Enter.
    2. In the Device Manager window, find and expand the Network adapters section.
    3. You will see a list of items. Look for your main adapter (it will likely have “Wi-Fi” or “Ethernet” in the name, like “Intel(R) Wi-Fi 6…”).
    4. Right-click on it and select Update driver.
    5. Choose Search automatically for drivers. Windows will try to find an updated driver.
    6. If it finds one, install it and restart your computer.

Method 10: Test in Safe Mode with Networking

This is a final, advanced diagnostic step. Booting your computer in “Safe Mode” starts it with only the essential drivers and services. No third-party applications, no startup items, no extra services. “Safe Mode with Networking” does this but also includes the basic drivers needed to connect to the internet.

  • Why it works: If the website loads in Safe Mode, you know 100% that the problem is not Windows, not your drivers, and not your hardware. The problem is some other piece of software you have installed that loads during a normal boot. This could be a background service, a startup utility, or a persistent piece of malware.
  • How to do it (Windows 10/11):
    1. Press the Windows key + R.
    2. Type msconfig and press Enter.
    3. Go to the Boot tab.
    4. Under “Boot options,” check the box for Safe boot.
    5. Below that, click the bubble for Network.
    6. Click OK and then Restart.
    7. Your computer will reboot into a black, low-resolution desktop. This is Safe Mode. Connect to the internet and test your browser.
    8. To get out of Safe Mode: Run msconfig again, go to the Boot tab, and uncheck the “Safe boot” box. Restart.

What If the Problem Isn’t You? (Server-Side DNS)

You’ve done it all. You’ve restarted, flushed, and reconfigured, and the error persists… but only for one specific website.

This is a strong sign that the problem is not with you; it’s with the website.

This often happens when a site has just launched or, more commonly, when it has just migrated to a new web host. The website’s owners or their technical team have to update their own DNS records to point the domain name to their new server’s IP address. If they make a mistake, or during the 24-48 hour “propagation” period where these changes are broadcast across the globe, their DNS can be broken.

The Web Host Migration Pitfall

As a web professional, I see this all the time. A business builds a beautiful new site on a platform like WordPress, but they use a separate, low-budget host. When they try to go live or migrate the site, their DNS settings (like A records and CNAME records) become a mess. The site is down for 48 hours, and they get stuck in a support loop, with the host blaming the domain registrar and the registrar blaming the host.

The Case for an Integrated Platform

This is where an all-in-one platform really shows its value. A fragmented setup creates multiple points of failure. The most reliable web experiences come from integrated systems where the components are built to work together.

For example, Elementor Hosting is a managed WordPress hosting solution built by the same team that builds the Elementor website builder. Because the builder, the platform, and the hosting are part of one unified system, these DNS conflicts are virtually eliminated. You build your site and host it in one place, with one point of support and one dashboard. It is a simple, robust solution that prevents these kinds of technical headaches from the start, so you can focus on your website, not on network configuration.

A Web Creator’s Perspective on DNS Stability

I spoke with digital marketing and web expert Itamar Haim about how he views these common DNS issues from a business perspective.

Itamar notes, “For a business, a ‘DNS Server Not Responding’ error isn’t just a technical glitch; it’s a ‘Closed for Business’ sign. It erodes customer trust and directly impacts revenue. Many creators focus on design and content, which are critical, but they forget the underlying foundation. Stable, fast, and correctly configured DNS is the bedrock of a professional online presence. An integrated solution, where your hosting and your site’s core files are optimized to work together, is one of the smartest investments a creator can make to ensure reliability and peace of mind.”

Frequently Asked Questions About DNS Errors

1. What is a DNS server in simple terms? It’s the internet’s “phonebook.” It translates human-friendly domain names (like google.com) into computer-friendly IP addresses (like 172.217.14.228).

2. Is it safe to change my DNS server? Yes. Changing your DNS to a reputable public provider like Cloudflare (1.1.1.1) or Google (8.8.8.8) is perfectly safe. In fact, it’s often more secure and faster than using your ISP’s default server.

3. Will changing my DNS make my internet faster? Sometimes. While it won’t increase your download speed (your bandwidth), a faster DNS server can make websites start to load faster because the initial “lookup” is quicker. This is called low-latency.

4. How do I know what my current DNS server is? The easiest way is to visit a site like whatsmydns.net. It will tell you your IP address and which DNS resolver you are currently using.

5. Why does this error happen on my phone? The same reasons! Your phone also has a DNS cache and DNS settings. This error is more common on Wi-Fi, as your phone is using the router’s DNS. You can fix it by restarting your phone, “forgetting” the Wi-Fi network and rejoining it, or (on Android) changing your DNS settings in the Wi-Fi connection’s details.

6. What’s the difference between flushing DNS and clearing browser cache?

  • Browser cache stores files from websites (images, HTML, CSS) to make the page load faster next time.
  • DNS cache stores only the IP addresses of websites. Flushing your DNS (Method 5) is different from clearing your browser’s cache (Method 3), and it’s important to try both.

7. Can a VPN cause this error? Absolutely. A VPN routes all your traffic through its own servers, and that includes DNS. If the VPN’s DNS server fails, your internet connection will stop working. This is why Method 8 (disabling secondary connections) is an important step.

8. Is 1.1.1.1 (Cloudflare) or 8.8.8.8 (Google) better? Both are excellent and far more reliable than most ISP servers. Cloudflare (1.1.1.1) generally wins on pure speed and has a strong focus on user privacy. Google (8.8.8.8) is known for its rock-solid reliability. You cannot go wrong with either.

9. What do the ipconfig /release and renew commands do?

  • ipconfig /release: This command tells your computer to “let go” of its current IP address, effectively disconnecting it from the local network.
  • ipconfig /renew: This command asks your router (or DHCP server) for a brand new IP address. This one-two punch is great for solving IP-related conflicts and is often done right after flushing the DNS.

10. If none of these 10 methods work, what’s next? If you have tried all 10 methods—especially changing your DNS server and power-cycling your router—and the problem still happens on all devices and all websites, it is time to call your Internet Service Provider (ISP). There is a very high chance they are experiencing a regional outage of their DNS or routing services, and only they can fix it.

Taking Back Control of Your Connection

The “DNS Server Not Responding” error is a roadblock that feels technical and intimidating, but in most cases, it’s highly fixable. The solution is almost always a “reset” of some kind.

By following these methods, you are systematically resetting each component of the connection: your browser (Method 3, 4), your computer’s “memory” (Method 1, 5), your network hardware (Method 2, 9), and your connection’s “phonebook” (Method 6). One of these steps will almost certainly clear the logjam and get you back online.