Win2k caches ip addr. after name resolution from dns?

[Tim Maestas]

	Win2k has a (horribly broken) caching client resolver.  If
	you are dealing with straight A records (no cnames) then it
	will cache the record for the life of the TTL attached
	to that record.  This is at the OS level.  There are a couple
	bugs that come along with CNAMES in relation to how Win2k
	caches the records that I will not go into here (it's in
	the archives somewhere)

	IE itself caches DNS responses as well.  Depending on your
	version, the cache time can range from 30 minutes to
	2 hours.  I don't know that this behaviour is configurable.

-Tim




On Mon, 24 Sep 2001, Sanjivendra Nath wrote:

> 
> Is there anyway for us to force the MS clients (namely, IE 5.0) to go to the
> DNS for name resolution always, or at least limit the time during which it
> caches the ip address of a site?
> 
> I've tried 4 clients now against my DNS running Bind9 on linux with
> roundrobin setup to 2 webservers behind it.
> 
> * linux client, win95, win98 - consecutive pings average out to 50% load on
> each webserver.
> 
> * win2k - consecutive pings sticks to the first ip address of the webserver
> served by my DNS.
> 
> Thanks,
> Sanju.
> 
> 
> 
>