[98507] in North American Network Operators' Group
RE: Content Delivery Networks
daemon@ATHENA.MIT.EDU (andrew2@one.net)
Fri Aug 10 11:15:30 2007
Reply-To: <andrew@profitability.net>
From: <andrew2@one.net>
To: "'Rodney Joffe'" <rjoffe@centergate.com>
Cc: "'NANOG'" <nanog@merit.edu>
Date: Fri, 10 Aug 2007 11:14:40 -0400
In-Reply-To: <89B50BEF-C94F-47D3-B096-D7D45D47C39B@centergate.com>
Errors-To: owner-nanog@merit.edu
Rodney Joffe wrote:
> On Aug 9, 2007, at 10:55 PM, Paul Reubens wrote:
>
>> How do you engineer around enterprise and ISP recursors that don't
>> honor TTL, instead caching DNS records for a week or more?
>>
>
> In my "little" bit of research and experience over the last 10 years
> in this field, I have often pursued this "urban myth". It remains
> largely just that.
>
> The most common supposed violator of this was AOL. I found myself in
> a position at one stage to get to the "root" of this, and was rather
> impressed to find that it was indeed a myth.
>
> We've just finished a small research project where we looked at
> approximately 16 million recursive servers. The only ones violating
> this were some CPE devices that ran local recursive services, and
> they were generally along the lines of returning the appropriate TTL
> the first time they were queried, and if the TTL was zero, they
> returned a higher TTL (10000 seconds) to subsequent queries for a
> short period (5 minutes). It may have been a code bug, or a designed
> behavior given that these were CPE devices.
Very interesting. We've all heard and probably all passed along that little
bromide at one time or another. Is it possible that at one time it was true
(even possibly for AOL) but with the rise of CDNs, policies of not honoring
TTL's have fallen by the wayside?
Andrew
