How to Clear Host Cache and Flush DNS in Microsoft Edge

When websites fail to load, display obsolete SSL certificate warnings, or resolve to old server IP addresses following DNS changes or web server migrations, most users attempt to resolve the issue by clearing standard browser cookies and browsing history. However, Chromium-based browsers like Microsoft Edge maintain their own internal DNS resolver cache and socket pools separate from your operating system’s DNS resolver. Even after running ipconfig /flushdns in Windows, Edge can continue serving stale IP mappings until its internal host cache is manually cleared.

Flushing Microsoft Edge’s Internal Host Resolver Cache

Microsoft Edge includes a hidden diagnostic URL panel that provides direct access to its networking stack. Clearing the host resolver cache forces the browser to discard cached IP lookups and query your configured network DNS servers afresh.

  1. Launch Microsoft Edge on your Windows, Mac, or Linux computer.
  2. Click inside the address bar (omnibox) at the top of the browser.
  3. Type the following internal URL and press Enter:
    edge://net-internals/#dns
  4. You will arrive at the DNS section of the Net-Internals diagnostic page.
  5. Locate the Host resolver cache section at the top of the page.
  6. Click the Clear host cache button.

The action executes immediately without a confirmation prompt. The browser wipes its internal table of resolved domain names and active IP mappings.

Closing Idle Sockets and Flushing Network Pools

Clearing the DNS table removes domain-to-IP records, but Edge may still maintain open, persistent TCP socket connections (Keep-Alive sessions) established with the older server IP address. To ensure complete disconnection from stale servers:

  1. While still in Microsoft Edge, enter the following address into your omnibox and press Enter:
    edge://net-internals/#sockets
  2. You will see the Sockets management panel.
  3. Click the Close idle sockets button.
  4. Click the Flush socket pools button directly beside it.

Closing idle sockets terminates lingering TCP/TLS handshakes, forcing Edge to re-initiate fresh network connections using updated DNS records on your next page load.

Flushing the Operating System DNS Cache in Windows 11

To eliminate discrepancies between your operating system and your browser, flush the Windows OS resolver cache immediately after clearing Edge’s host cache:

  1. Press Windows Key + X and select Terminal (Admin) or PowerShell (Admin).
  2. Type the following command and press Enter:
    ipconfig /flushdns
  3. Windows will display: “Successfully flushed the DNS Resolver Cache.”
  4. You can also release and renew your local DHCP network lease by running:
    ipconfig /release && ipconfig /renew

Disabling Secure DNS (DoH) Interference

Microsoft Edge features built-in Secure DNS (DNS over HTTPS). If Secure DNS is enabled using a third-party upstream resolver (such as Cloudflare or Google Public DNS), Edge bypasses your local network’s DNS server entirely. If your organization relies on local intranet domain routing or split-horizon DNS:

  1. In Microsoft Edge, click the three dots in the top-right corner and select Settings.
  2. Click on Privacy, search, and services in the left sidebar.
  3. Scroll down to the Security section.
  4. Under Use secure DNS to specify how to look up the network address for websites, verify whether a custom provider is selected.
  5. If testing local or staging server domains, temporarily select Use current service provider to ensure Edge respects your operating system’s local hosts file and network router DNS.

Get the best tech tips delivered straight to your inbox.

Join thousands of readers mastering Apple, Google, Microsoft, and Linux.