If you are experiencing "Site cannot be reached" errors or seeing an outdated version of a website after a server migration, the solution is often running a simple command in the Windows Command Prompt. The specific command to clear the DNS cache in Windows is ipconfig /flushdns.

Executing this command forces your computer to discard its local database of domain-to-IP mappings and request fresh information from the DNS server the next time you visit a website. While the process takes only a few seconds, understanding how the DNS resolver cache works and when to supplement this with other troubleshooting steps is essential for maintaining a stable internet connection.

How to Execute the DNS Flush Command in Windows CMD

The most reliable way to perform a DNS flush is through the Command Prompt (CMD) with administrative privileges. Without these elevated permissions, Windows may block the system from modifying network parameters, leading to an "Access Denied" error.

Step-by-Step Instructions for Windows 10 and Windows 11

  1. Open the Start Menu: Press the Windows key on your keyboard or click the Start icon.
  2. Search for CMD: Type cmd or Command Prompt into the search bar.
  3. Run as Administrator: Right-click the Command Prompt application from the search results and select Run as administrator. This is a critical step because modifying the DNS Resolver Cache is a system-level task.
  4. Enter the Command: In the black window that appears, type the following command exactly as shown: ipconfig /flushdns
  5. Press Enter: Once you press Enter, the system will process the request.
  6. Verify Success: Within a second, you should see a confirmation message: "Successfully flushed the DNS Resolver Cache."

Running the Command on Older Windows Versions

While Windows 7 and Windows 8 are no longer officially supported by Microsoft for general consumers, many legacy systems still rely on them. The process is nearly identical:

  • In Windows 7, you can find CMD by navigating to Start > All Programs > Accessories, then right-clicking Command Prompt.
  • The command ipconfig /flushdns remains the same across all versions of Windows NT-based operating systems.

What is DNS Cache and Why Does It Get Corrupted?

To understand why a DNS flush is necessary, you must first understand the role of the Domain Name System (DNS). The internet operates on IP addresses (like 192.0.2.1), but humans prefer domain names (like example.com). DNS acts as the "phonebook" of the internet, translating names into numbers.

The Role of the DNS Resolver Cache

Every time you visit a website, your computer performs a DNS lookup. To save time and reduce network traffic, Windows stores the results of these lookups in a local temporary database called the DNS Resolver Cache. The next time you visit the same site, Windows checks the local cache first. If a record is found, the browser connects to the site instantly without querying an external DNS server.

Causes of Stale or Corrupted Data

In an ideal world, this cache would always be accurate. However, several scenarios can cause the cache to become a liability:

  • IP Address Changes (Server Migration): If a website owner moves their site to a different hosting provider or server, the IP address changes. If your computer still has the old IP address cached, it will try to connect to a server that no longer hosts the site, resulting in a 404 error or a connection timeout.
  • DNS Spoofing (Cache Poisoning): This is a security risk where a malicious actor "poisons" your cache with incorrect IP addresses. They might redirect your request for a legitimate banking site to a fraudulent clone. Flushing the DNS cache removes these malicious entries.
  • Corrupted Records: Network glitches or software bugs can occasionally lead to malformed records in the cache, causing "unknown host" errors even when the internet is otherwise working fine.

Technical Analysis of the ipconfig Command

The ipconfig utility is one of the oldest and most versatile networking tools in Windows. While /flushdns is the most popular switch for casual users, understanding the surrounding commands provides a more comprehensive diagnostic capability.

Exploring the /displaydns Switch

Before you flush your cache, you might want to see what is actually inside it. By running ipconfig /displaydns, you can view the entire list of domain names currently stored in your local resolver.

In our practical testing, this output can be quite long. Each entry shows:

  • Record Name: The domain you visited.
  • Record Type: Usually "A" (for IPv4 addresses) or "AAAA" (for IPv6).
  • Time To Live (TTL): This is a countdown in seconds. When it reaches zero, the record is naturally purged from the cache.
  • Data Length: The size of the record.
  • Section: Usually "Answer."

If you run /displaydns and see a specific website mapped to an IP that you know is incorrect, you have confirmed that a flush is the correct course of action.

The Role of /registerdns

Sometimes, flushing the DNS isn't enough because the problem isn't with what your computer remembers, but with what the network knows about your computer. The ipconfig /registerdns command refreshes all DHCP leases and re-registers DNS names. This is particularly useful in corporate environments where your computer needs to update its own record on the company's DNS server.

Troubleshooting Common DNS Flush Errors

While the command is straightforward, certain system configurations can cause it to fail.

Handling the "Access Denied" Error

If you see a message saying "The requested operation requires elevation," it means you opened CMD as a standard user. Windows protects the DNS Resolver Cache because clearing it affects all users on the machine. Always ensure the title of your CMD window starts with "Administrator: Command Prompt."

"Could Not Flush the DNS Resolver Cache: Function Failed During Execution"

This is a rarer but more frustrating error. It typically occurs if the DNS Client service has been disabled. Windows relies on this service to manage the cache.

To fix this:

  1. Press Win + R, type services.msc, and press Enter.
  2. Find the DNS Client service.
  3. Ensure the Status is "Running."
  4. If it is stopped and the options are greyed out, you may need to use the Registry Editor to re-enable it (though this is only recommended for advanced users).

When the Command Runs but Nothing Changes

If you run ipconfig /flushdns and still see the old website, the problem might not be the Windows cache. Modern internet browsing involves multiple layers of caching:

  1. Browser Cache: Google Chrome, Mozilla Firefox, and Microsoft Edge have their own internal DNS caches that are independent of Windows.
  2. Router Cache: Your home or office router often maintains its own DNS cache.
  3. ISP Cache: Your Internet Service Provider (ISP) caches DNS records to save bandwidth.

If a system-level flush fails, we recommend restarting your router or checking your browser's specific internal DNS settings.

Comparing CMD and PowerShell for DNS Management

For users who prefer the modern Windows environment, PowerShell offers an alternative way to manage the DNS cache. While CMD is classic and universal, PowerShell is more powerful for automation.

The PowerShell Command: Clear-DnsClientCache

Instead of ipconfig /flushdns, you can use: Clear-DnsClientCache

Pros of PowerShell:

  • Scripting Integration: You can easily include this command in a .ps1 script to automate network maintenance.
  • Object-Oriented: PowerShell treats network data as objects, making it easier to filter results (e.g., finding only records with a specific TTL).

Pros of CMD:

  • Speed: CMD loads faster than PowerShell.
  • Compatibility: ipconfig works on literally every version of Windows since the 1990s.

In a professional support environment, we typically recommend the CMD version first because it is less likely to be blocked by restrictive execution policies often found in corporate PowerShell environments.

The Impact of DNS Flushing on Network Performance

A common question among users is whether flushing the DNS cache will slow down their internet. The short answer is: minimally and temporarily.

When you clear the cache, your computer must "start over" for every website you visit. The very first time you go back to a site after a flush, there will be a slight delay—usually a few milliseconds—as your computer contacts an external DNS server to get the IP address. Once that lookup is complete, the record is placed back into the cache, and subsequent visits will be just as fast as before.

In our experience, this "performance hit" is imperceptible to the human eye on modern high-speed connections. The benefit of resolving connectivity issues far outweighs the microsecond delay of a fresh DNS lookup.

Advanced Usage: Automating the DNS Flush

If you work in a development environment where IP addresses change frequently (for example, when working with Docker containers or rotating cloud instances), you might find yourself running the flush command multiple times a day. You can automate this process using a Batch file.

Creating a "Refresh Network" Script

  1. Open Notepad.
  2. Paste the following lines: 
    @echo off
ipconfig /flushdns
ipconfig /release
ipconfig /renew
echo DNS Flushed and IP Reset.
pause
  3. Save the file as refresh.bat.
  4. To run it, right-click the file and select Run as Administrator.

This script not only clears the DNS cache but also drops your current IP address and requests a new one from your router (DHCP). This is often the "nuclear option" for fixing stubborn home internet issues.

When Should You Use a DNS Flush?

Flushing the DNS is a targeted tool, not a cure-all for every internet problem. Use it in the following specific scenarios:

  • Website Developers: When you change the "A record" for a domain in your registrar (like GoDaddy or Namecheap), you need to flush your local cache to see the changes immediately.
  • Public Wi-Fi Users: If you switch from a home network to a coffee shop Wi-Fi, the local cache might still hold internal IP addresses from your home network.
  • Privacy Seekers: The DNS cache is a record of your browsing history. While not as easy to read as browser history, someone with access to your CMD could run ipconfig /displaydns to see which domains you've been visiting. Flushing it clears this trail.
  • Fixing "DNS_PROBE_FINISHED_NXDOMAIN": This specific Chrome error is almost always resolved by a combination of a CMD flush and a browser restart.

Summary of Key Points

  • The primary command is ipconfig /flushdns.
  • It must be run in an Elevated Command Prompt (Admin mode).
  • It solves issues related to outdated IP addresses and DNS corruption.
  • It is completely safe and will not harm your files or settings.
  • If CMD doesn't work, the issue may reside in your browser's internal cache or the router.

FAQ

Does flushing DNS delete my browsing history?

No. Flushing the DNS cache only removes the IP address mappings for the domains you have visited. It does not delete your browser's history, saved passwords, or cookies.

Do I need to restart my computer after flushing the DNS?

Usually, no. The changes take effect immediately. However, you should restart your web browser to ensure it picks up the changes to the system-level cache.

Can I flush DNS on a Mac or Linux?

Yes, but the commands are different. On macOS, you would typically use sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. On Linux, it depends on the DNS service being used (such as systemd-resolved or nscd).

How often should I flush my DNS?

There is no need to do this on a schedule. You should only run the command when you are experiencing specific connection issues or when you know a website has changed its server.

What is the difference between ipconfig /release and ipconfig /flushdns?

/flushdns clears the "phonebook" of website names. /release tells your router that you are giving up your current IP address on the local network. They solve different types of problems.

Will flushing DNS fix a slow internet connection?

Probably not. Slow speeds are usually caused by bandwidth congestion, signal interference, or ISP throttling. Flushing DNS only helps if the "slowness" is specifically caused by the computer struggling to resolve the initial website address.

Is there a way to flush DNS without using the command line?

You can technically achieve a similar result by disabling and re-enabling your network adapter in the Windows Control Panel, but the CMD method is much faster and more thorough.