Jan 27 2020 05:34 AM - edited Jan 27 2020 12:27 PM
I ran into a persistent "resolving host" issue on one of my computers this weekend and worked my way through the usual resolution steps (W10 DNS flush (ipconfig /flushdns), browser DNS flush and so on) in order to clean up the various DNS caches and start with a clean slate.
It does not appear that Edge DNS flush (edge://net-internals/#dns, similar to chrome://net-internals/#dns or opera://net-internals/#dns) is operative.
The "Clear host cache" button shows up but doesn't seem to be functioning:
I don't know if this is a bug or a feature, but it is a difference from other Chromium-based browsers I've had the occasion to use.
Feb 05 2020 11:14 AM
@tomscharbach Thanks for reaching out, Tom! I brought this back to the team and they didn't have an immediate answer. @ericlaw , do you have any insight into this?
Fawkes (they/them)
Project & Community Manager - Microsoft Edge
Feb 05 2020 11:21 AM
@tomscharbach Thanks for the note!
Can you elaborate on your determination that the button doesn't work? What sort of testing did you do?
Notably, the button provides no feedback of completion, and is styled in such a way in Edge that it is more likely to appear that clicking it hasn't actually "pushed" the button. But it does dispatch the clearHostResolverCache call to the browser.
Jun 11 2020 06:00 PM
@tomscharbach I found the same "issue" you likely saw. Not only did I need to ipconfig /flushdns and edge://net-internals/#dns but also Ctrl+F5 on the website in questions.
Jul 10 2021 10:28 AM
Jul 10 2021 05:35 PM
Aug 25 2021 01:20 PM
Feb 09 2022 11:26 AM
I have recently been dealing with this when we are testing multiple web front ends for our student information system.
We change the DNS in our hosts file.
Then we have to run ipconfig /flushdns
Next step is to edge://net-internals/#dns go here and Clear Host Cache
Next go to edge://net-internals/#sockets and Close Idle Sockets and Flush Socket Pools.
Then we go to the website it will use the IP address from the hosts file.