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...
Eric_Lawrence
Microsoft
MicrosoftI happy to take a look at your NetLog where you found edge://net-internals/#dns was ineffective.
Keep in mind that if you have an active (reusable) connection to the site, I'm not sure that flushing the browser's DNS cache will close that connection.
Keep in mind that if you have an active (reusable) connection to the site, I'm not sure that flushing the browser's DNS cache will close that connection.
I had a similar problem and determined that occurred when the target host's ip address changed after it had been resolved by a secondary DNS server. I thiis case I have a split DNS setup and the local DNS server did not respond with the local address for the host. The internet server responded with the domain's public IP address which cannot be used to reach the internal server. Flushing the did not resolve the issue. Closing and reopening Edge also did not resolve the problem. I changed Edge settings so all processes end when you close the app. Closed the app and restarted. At that point the local address was retrieved from the local DNS server and the connection was made.
Based on Eric_Lawrence's comment it would appear that the DNS client is not being consulted even when opening a new window. It's as if Edge has created something that behaves like a cache although it appears that it's reusing connections. The problem is that it doesn't seem to know that the server's address has changed even if the server is currently unreachable.
Perhaps the Edge should lookup the address from time-to-time and avoid reusing of stale addresses.
Based on Eric_Lawrence's comment it would appear that the DNS client is not being consulted even when opening a new window. It's as if Edge has created something that behaves like a cache although it appears that it's reusing connections. The problem is that it doesn't seem to know that the server's address has changed even if the server is currently unreachable.
Perhaps the Edge should lookup the address from time-to-time and avoid reusing of stale addresses.
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.
