Forum Discussion
Edge: DNS Flush
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 o...
I still don't understand how it can be so hard to just fully refresh a website.
It feels like I have to jump through thirty hoops just to get edge motivated enough to refresh a god-**bleep** DNS entry that should simply be refreshed with a single button press. Every other browser detected the change in DNS just fine.
It makes Edge almost impossible to use within active Development circles. I really hope someone will find a proper way to get Edge to behave.
Eric_Lawrence
Microsoft
MicrosoftMany things seem like they should be "simple" but are quite complicated if you look at the full set of components involved.
Which DNS resolver are you configured to use? Beyond the DNS cache in the browser, the OS maintains its own cache of DNS resolutions. Did you clear that? Do you have a NETLOG showing a cached DNS record being used? Did you already have active connections to the hostname in question in the browser's keep-alive pool?
