Hi Alistair, it was ages since I used Windows so I am not sure what has happened in later versions of Windows, but I do know that Microsoft used to have a buggy resolverlib that ignored the TTL and assumed that it was always 86400 (24h). After trying to use some short TTL:s in the year 2001 I had to give up on it because of having too many Microsoft machines not working properly with that resolving. So sorry, no help with the issue, but as a rule of thumb I would only use PAT/NAT on the firewall and similar techniques for failover because of such issues. I wouldn't be surprised if a lot of web proxies will override DNS TTL info aswell - I am quite sure you can set this manually in Squid for instance. Regards, Carl On Mon, Jun 08, 2009 at 12:34:31PM +0100, Alastair Broom wrote: > > So we have some domains with a 5 minute TTL being given out from bind > 9.3.4-2etch3 on a datacentre server. 5 minutes so we can quickly switch > servers in the event of a server outage. > > 99% of our customer sites are fine. But a couple of sites, who have MS > Windows 2000 DNS servers, have problems looking up the names. > Occasionally they manage to map the name to the number. Mostly, Internet > Explorer reports DNS name not found. > > The domains were looked up okay by W2000 when they had a 24h TTL, but we > don't really want to increase the TTL (much). > > ???Anyone come across this ? > > Thanks > -- > Al > > > - > ---------------------------------------------------------------------- > You can find the EdLUG mailing list FAQ list at: > http://www.edlug.org.uk/list_faq.html - ---------------------------------------------------------------------- You can find the EdLUG mailing list FAQ list at: http://www.edlug.org.uk/list_faq.html
|
This archive is kept by wibble+RM@xxx.xxx.xxx Morpheux | HomePage |