Proxy & DNS cache
wolruf
I have the following issue and wonder how to solve it:
- I have Mozilla on Win2k setup with a proxy as a host name called
"proxy",
- I connect to a HotSpot[1] where my proxy is transparently handled
(i.e. spoofed to 1.1.1.1 for eg., usually with a low DNS TTL: 1),
- I launch a VPN client which connect me with a new IP address and new
DNS settings (new search string and DNS IP address),
- the proxy should now resolve to "proxy" + the default search string
"corporate.com" -> proxy.corporate.com which then resolve to 172.16.1.1.
- however, Mozilla doesn't re-resolve "proxy" to be used as proxy and
still use the old IP address for this host (1.1.1.1),
- I have to restart Mozilla to "reset" the proxy host to its new IP
address.
I looked at the code and cannot see if there's a way for the proxy host
resolution to respect the DNS TTL.
All DNS requests work fine, it's just that the proxy host got "cached".
Is there anyway for Mozilla to know that the DNS settings changed and he
has to re-resolve the proxy hostname just once (obviously, he shouldn't
re-resolve for every request) ?
IE6 has the same issue.
Mozilla on Linux may behave different as it has it own DNS resolver but
I guess the proxy host will also be cached for the whole session.
This is more and more frequent with HotSpots implementing this kind of
plug-n-play feature.
Olivier.
PS: It's a coincidence that Darin actually talk about a DNS rewrite in
his blog :)
[1] HotSpot example: StarBucks coffee, etc.