Locahl
Buy Locahl
DNSMicrosoft EdgecacheWindowshosts file

Clear DNS Cache in Microsoft Edge (2026)

Clear the DNS cache in Microsoft Edge with edge://net-internals/#dns, flush socket pools, and clear the Windows DNS cache so hosts changes take effect.

L

Locahl Team

·2 min read

Table of Contents

To clear the DNS cache in Microsoft Edge, open edge://net-internals/#dns, click Clear host cache, then flush socket pools. Do this when Edge keeps loading the old IP after you changed the hosts file or DNS settings.

How to clear the DNS cache in Microsoft Edge

Follow these steps in order:

1. Open a new tab and go to edge://net-internals/#dns. 2. Click Clear host cache. 3. Switch to the Sockets section (edge://net-internals/#sockets) and click Flush socket pools. 4. Flush the Windows DNS cache too: open Command Prompt as administrator and run ipconfig /flushdns — see flush DNS on Windows. 5. Close and reopen the tab (or restart Edge) and reload the page.

Because Edge is Chromium-based, the same steps work in Chrome at chrome://net-internals/#dns.

Why clearing Edge alone is not enough

Edge caches DNS results in memory, but Windows keeps a separate resolver cache. If you only clear Edge, the OS may still serve the old IP. Always pair the browser flush with ipconfig /flushdns.

When to do this

  • You edited C:\Windows\System32\drivers\etc\hosts and Edge opens the old site.
  • You changed DNS servers or connected to a VPN.
  • A staging site moved to a new server before propagation.

For the editing workflow, see edit the hosts file on Windows.

Verify it worked

TEXT
nslookup myproject.test

If nslookup shows the correct IP but Edge still does not, repeat the host cache and socket pool flush, then reopen the tab in a fresh window.

Troubleshooting

  • Old site persists: keep the device awake and reload; some connections stay alive briefly.
  • Only Edge affected: restart Edge fully (check background processes in Task Manager).
  • Wrong IP returned: re-check the hosts line — see the syntax guide.

If you change local domains often, Locahl edits the hosts file safely and flushes DNS automatically, so you rarely need to clear the browser by hand.

_Last tested: June 2026 in Microsoft Edge on Windows 11._

Also readFlush DNS on Windows 10 and 11
Also readHow to edit the hosts file on Windows
Share this article
Available on Windows, macOS & Linux

Ready to simplify your workflow?

Stop wasting time with the terminal. Locahl lets you manage your hosts file in a few clicks, with automatic validation and no risk of errors.

  • Intuitive visual interface
  • Automatic DNS flush
  • Multi-environment management
  • Automatic backups
  • JSON Import/Export
Buy Locahl — $5.99One-time payment, no subscription

Reader Reviews

4.7★(3 reviews)
Marcus L.
★★★★★

"edge://net-internals/#dns plus socket pools flush fixed my stale local domain in Edge."

June 12, 2026

Yara S.
★★★★★

"Clear, exact steps. The reminder to also flush Windows DNS was the missing piece."

June 10, 2026

Erik N.
★★★★★

"Worked great. Could mention Edge on macOS too."

June 8, 2026

Frequently Asked Questions

How do I clear the DNS cache in Microsoft Edge?

Open edge://net-internals/#dns, click Clear host cache, then go to the Sockets tab and click Flush socket pools.

Do I also need to flush the Windows DNS cache?

Yes. Edge keeps its own cache, but the OS caches DNS too. Run ipconfig /flushdns for changes to fully apply.

Why does Edge still load the old site after a hosts change?

Edge cached the old resolution and may keep a live connection. Clear the host cache, flush socket pools, and reopen the tab.

Related Articles

10 min read
hosts fileWindowsmacOS

How to Edit the Host File (Windows, Mac & Linux)

Edit the host file on Windows, macOS and Linux: file location, admin rights, syntax, DNS flush, and troubleshooting when changes do not apply.

L

Locahl Team

5 min read
ChromeDNSmacOS

Clear Chrome DNS Cache on Mac Fast

Clear Chrome DNS cache on Mac with chrome://net-internals, flush macOS DNS, restart sockets and fix stale local domains after hosts changes.

L

Locahl Team

Developer tools team

2 min read
localhost127.0.0.1DNS

127.0.0.1 vs localhost: What’s the Difference?

127.0.0.1 vs localhost explained: both point to your machine, but they differ in DNS resolution, IPv6, and hosts file behavior. When to use each, with examples.

L

Locahl Team

Developer tools team

2 min read
hosts fileWindowseditors

Best Hosts File Editors for Windows (2026)

The best hosts file editors for Windows in 2026: Locahl, Notepad as admin, Hosts File Editor+, SwitchHosts and BlueLife Hosts Editor. Pros, cons and when to use each.

L

Locahl Team

Developer tools team