DNS Cache Resolver overrides NS TTLs
connah at gmail.com
Wed Sep 6 13:38:24 UTC 2006
Would some please explain to me why Microsoft's DNS Cache Resolver has
it's own built in TTL defaulting to 86400 (24 hours) instead of paying
attention to the TTL that the domain's name server reports? This is
very frustrating to me. We set our TTLs on our domains in BIND to be
3600 (1 hour) so we can change our records and it get updated quickly.
However, Windows caches names for a day without regard to that setting.
It seems that since Windows being as ubiquitous as it is, the TTL
setting on an SOA record is meaningless.
I'm not just griping; I am truly hoping that I am wrong and someone
will set me straight. I would ultimately like to have control over how
long a client caches my domain's IP but it seems like Windows overrides
me. Thanks for any input!
More information about the bind-users