On Aug 10, 2007, at 9:13 AM, Max Inux wrote:
Working for a content delivery network I can tell you that there are many nameservers ignoring TTL that affect many users (AOL being the largest american one). Coincidentally AOL users aren't nearly so affected by that as they are that their data goes to Virginia to enter the internet negating close-to-end-user acceleration benefits.
Additionally there are several networks off of Singtel (Singapore/ Southern asia/oceania), Many in Australia (Likely due to Squid caches to prevent egress), and in Europe (Mostly France) that I have specifically ran into that had this disregard for TTL impact them. In short, they are out there, and they will bite you from time to time if your network is widely enough used.
Specifics? Off list is fine.
On Aug 10, 2007, at 9:13 AM, Max Inux wrote:
Working for a content delivery network I can tell you that there are many nameservers ignoring TTL that affect many users (AOL being the largest american one). Coincidentally AOL users aren't
So, I'd also ask this, do you know it's the recursive server, or is the behavior that you see related more to the application caching and not respecting the TTL? (IE for instance and it's default 30 minute, I think, ttl). How does a CDN tell the recursive server is doing this vice the client app?
participants (2)
-
Chris L. Morrow
-
Rodney Joffe