 |  |
> From: "andrew kagan" <andrew@ardentmicro.com>
Re: TTLs and Caches
From: George Ruzzier
Date: Tuesday, July 23, 2002
Time: 1:08:15 pm
> Date: Tue, 23 Jul 2002 14:28:55 -0400
>
> two weeks is a long time...and I assume your original TTLs were not
set
> longer than that <g>
No, they were set to 1 day.
>
> Did you adjust the global TTL or individual record TTLs (or both)?
Individual records. Where is the global TTL setting??
>
> Some poorly designed proxy servers ignore TTLs and sometimes refuse
to
> release IPs until their caches are manually flushed or they're
restarted,
> which might have explained the problem you experienced.
>
> Microsoft Proxy Server was infamously problematic...And then there's
AOL's
> proxies....
>
> It would be useful to know what the people with problems were using to
> reach your site...dialup, corporate connection behind firewall or
proxy, etc.
> You may never get 100% recognition
I spoke today with an associate who mentioned that lowering to 300 is
not a good strategy as many resolvers will ignore as it is too low.
Instead, he suggested lowering to 7200, then the day before 1500 to
gradually take it down.
I think personally, I will just move the old server to a new ip address
and put the new server at the old server ip to avoid any issues.
Nothing like getting flooded with calls from people who can't connect to
check mail.
Thanks for your help.
Messages In This Thread:
Return to Digital Point Solutions' Home Page