Can someone please clarify how IE11 cache interacts with DNS resolver?
Is there a way to force IE to honor the DNS TTLs and submit another dns query ?
While testing OWA exchange 2016 with IE 11 on both windows 7 and windows 10, it appears the browser is not honoring the DNS TTL.
For example:
OWA url =exchange-test.xyz.com is a cname to exchange-test.wlb.xyz.com with a TTL 1
A site balancer will round robin testers to either data center 1 (DC1) and data center 2 (DC2), depending upon their health.
When DC1's exchange's VIP is brought down, the expectation is the tester will refresh their browser and reconnect to DC2.
This does not happen. A 'page cannot be displayed' occurs.
A NSLOOKUP query of domain exchange-test.xyz.com replies with DC2 VIP. BIGIP LTM & Site balancer confirm DC1 is DOWN. Yet, the browser does not query DNS again. Only when cache is cleared and all open IE browsers are closed and new IE window opened, then it will connect to DC2.
Is there a way to force IE to honor the DNS TTLs and submit another dns query ?
While testing OWA exchange 2016 with IE 11 on both windows 7 and windows 10, it appears the browser is not honoring the DNS TTL.
For example:
OWA url =exchange-test.xyz.com is a cname to exchange-test.wlb.xyz.com with a TTL 1
A site balancer will round robin testers to either data center 1 (DC1) and data center 2 (DC2), depending upon their health.
When DC1's exchange's VIP is brought down, the expectation is the tester will refresh their browser and reconnect to DC2.
This does not happen. A 'page cannot be displayed' occurs.
A NSLOOKUP query of domain exchange-test.xyz.com replies with DC2 VIP. BIGIP LTM & Site balancer confirm DC1 is DOWN. Yet, the browser does not query DNS again. Only when cache is cleared and all open IE browsers are closed and new IE window opened, then it will connect to DC2.