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 also had a resolving host problem, which I solved in the end by deleting all site data in edge://settings/siteData . Some DNS info probably is stored there which doesn't get deleted with DNS flush? (some other comment suggested it has to do with internet explorer mode -https://learn.microsoft.com/en-us/answers/questions/652141/edge-is-not-woking-properly-for-a-particular-dns-u )
- Eric_Lawrence
Microsoft
Menoblack That should not be the case, no. If anything, it should be the opposite (if you have a web page entirely in the cache, or if you have a serviceworker installed by the target site, your browser might not need to connect to the server at all).
If you have a NetLog (https://textslashplain.com/2020/01/17/capture-network-logs-from-edge-and-chrome/) from your failing scenario, you could look to see what precisely is happening with DNS resolutions.
Eric_Lawrence I took a look, but I don't see a lot of differences, the request before the change had +URL_REQUEST_DELEGATE_CONNECTED [dt=1] (dt=0 after) and HTTP_CACHE_CREATE_ENTRY [dt=0] (dt=1 after). Maybe the site is loaded from cache even though I used ctrl f5? I see in some other topic that might be because that site has the Cache-Control: no-store, no-cache, must-revalidate headers, which work against eachother - nginx - My browser keeps showing cached page despite sending no-cache, no-store, must-revalidate from server in response header - Server Fault . Could that be a reason?
ps. I've tried 3 more times, to let the correct site load I need to clear the host cache on edge://net-internals/#dns , and then delete edge://settings/siteData after. (now a browser reboot also works, that wasn't the case the first time.)
ps2. not posting the net export here because of privacy reasons 🙂
- Eric_LawrenceThere's nothing wrong with sending that set of Cache-Control headers; they'll be treated as |no-store|. Having said that, Cache-Control headers don't apply to every layer of caching in the browser, so they're not a complete guarantee against reuse of a response. But on a full-page navigation, they should be effective.
The thing you want to look at in the netlog is the DNS transaction entries.
