The problem is that it doesn't seem to know that the server's address has changed even if the server is currently unreachable. It's as if Edge has created something that behaves like a cache although it appears that it's reusing connections. At that point the local address was retrieved from the local DNS server and the connection was made.īased on comment it would appear that the DNS client is not being consulted even when opening a new window. I changed Edge settings so all processes end when you close the app. Closing and reopening Edge also did not resolve the problem. The internet server responded with the domain's public IP address which cannot be used to reach the internal 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. This improvement is made by a browser cache that consists of files and other data previously stored on your hard drive.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. This process is quicker on your second or third visit to a page.
This doesn't occur while the InPrivate Browsing mode is active.
0 kommentar(er)
