In this guide, you will learn how to inspect, clear, and test the DNS cache in Windows 11 using Command Prompt and PowerShell, and what to do if flushing DNS does not fix the issue.

What is the DNS cache?

DNS (Domain Name System) translates website names into IP addresses. The Windows DNS Client caches some lookup results, including negative responses. This is useful for performance, but cached records can sometimes be outdated after a website or network changes. Flushing the cache removes those saved DNS-client records; it does not delete files, browser history, passwords, or change the DNS server configuration.

Method 1: Flush DNS with Command Prompt

1. Open the Start menu, type Command Prompt, and select Run as administrator. Approve the User Account Control prompt.
2. Enter the following command:

ipconfig /flushdns

Windows should respond with Successfully flushed the DNS Resolver Cache. This confirms the cache-clearing command completed, not that the underlying internet problem is fixed.

Check the existing cache before clearing it

If you want to see entries first, open Command Prompt and run:

ipconfig /displaydns

The list may be long. You can also export it for review:

ipconfig /displaydns > "%USERPROFILE%\Desktop\dns-cache.txt"

This example writes a local text file containing cached DNS data to your desktop. Avoid publicly sharing the exported file because it can reveal domains accessed by applications.

Method 2: Clear DNS cache using PowerShell

1. Right-click the Start button and open Terminal (Admin) or Windows PowerShell (Admin).
2. In a PowerShell tab, enter:

Clear-DnsClientCache

The command typically finishes without displaying a success message. To inspect the client cache before or after clearing, use:

Get-DnsClientCache

A small or empty list immediately after clearing can be normal; entries return as Windows and applications perform new lookups. If Clear-DnsClientCache is not recognized, make sure you are in a Windows PowerShell environment with the DnsClient module rather than another shell.

Method 3: Check whether DNS resolution works

After clearing the cache, test resolution independently of your browser. Open Terminal and run:

nslookup www.microsoft.com

Look for an address in the response. nslookup queries a DNS server and is useful for testing DNS resolution, but it does not prove every website connection will work. You can also use PowerShell:

Resolve-DnsName www.microsoft.com

To compare your PC’s default DNS behavior with a chosen public resolver, you can optionally run:

nslookup www.microsoft.com 1.1.1.1

Privacy note: That final test sends a DNS query to Cloudflare’s public resolver. On a workplace network, follow your organization’s policy and use its approved DNS servers instead.

What if flushing DNS does not solve the problem?

1. Confirm you have a working connection

Check the Wi-Fi or Ethernet icon and try a few unrelated websites. If none work, investigate connectivity before focusing on DNS. See our related guide: Windows 11 Wi-Fi Connected but No Internet? 9 Fixes to Try.

2. Inspect the configured DNS servers

In PowerShell, run:

Get-DnsClientServerAddress -AddressFamily IPv4

The output lists the DNS servers configured on each network interface. Corporate PCs may use internal DNS servers to resolve Active Directory resources, so do not replace them with public addresses without approval.

3. Consider browser DNS caches

Some browsers and applications cache lookups independently or use secure DNS. Close and reopen the affected browser, then retry. If an issue occurs only in one browser, check its secure-DNS settings and extensions before changing Windows network settings.

4. Check VPN, security software, and the hosts file

A VPN, filtering application, proxy, or custom hosts-file entry can influence name resolution. On managed devices, speak with IT before modifying these settings. Flushing the Windows cache will not override a hosts-file mapping or repair a broken DNS server.

5. Restart the computer if necessary

A restart can help when a program is holding outdated connection state. Avoid resetting the full network stack as a first step: those changes are broader than flushing DNS and can disrupt VPN or enterprise settings.

Frequently asked questions

Is flushing DNS safe?

Yes, in normal circumstances. It discards cached DNS-client results and allows fresh lookups. The next visit to a domain may require an additional DNS query.

Does clearing DNS make internet faster?

Not generally. DNS caching normally improves performance. Flushing is a targeted troubleshooting step for stale or problematic records, not a general speed optimization.

Do I need to change my DNS servers?

No. Clearing the cache and changing which DNS server your computer uses are different actions. Try diagnosing the existing DNS service first.

Quick reference

Further reading: Microsoft: ipconfig, Microsoft: Clear-DnsClientCache, and Microsoft: Get-DnsClientCache.

Featured image credit: Albert Stoynov / Unsplash. The image illustrates network infrastructure; command examples above are text for accurate copying rather than simulated screenshots.

The post How to Flush DNS Cache in Windows 11 (Command Prompt and PowerShell) first appeared on ElMajdal.net.