On Jan 11, 2008 9:01 PM, Vipul Mathur <[EMAIL PROTECTED]> wrote: > On Jan 11, 2008 4:55 PM, आशीष शुक्ल Ashish Shukla <[EMAIL PROTECTED]> wrote: > > I just found that www.intel.com has TTL of 60s, and in my view TTL of > > 60s should be suitable for records with frequently changing IPs, e.g. > > for DNS records maintained by DynDNS users who're on dynamic IPs. > > Hmm...? > > Note in your dig trace that the 60s TTL is for the CNAME record > pointing www.intel.com to www.intel.com.edgesuite.net. Now > edgesuite.net is an akamai service AFAIK. > > The purpose of keeping a very short TTL, as far as I see, is to > prevent downstream DNS servers from caching it for a long time > (obviously). This would typically be done if the record gets updated > frequently... but hey, akamai is known to do weirdly interesting > stuff!
<disclaimer> I work for Akamai and am not speaking for my employer Blah blah blah </disclaimer> Akamai has a globally distributed server network. It maps users to these servers depending on a variety of factors such as geographic location, network latency, server load etc. One of the ways this works is that by recomputing the DNS entries based on these. As such factors are highly variable, the TTL is small so that users are mapped to the most optimal server everytime. Shameless plug follows :-) I agree with Vipul. Akamai does fairly interesting stuff. -- Vinayak -- http://www.linkedin.com/in/VinayakH _______________________________________________ ilugd mailinglist -- ilugd@lists.linux-delhi.org http://frodo.hserus.net/mailman/listinfo/ilugd Next Event: http://freed.in - February 22/23, 2008 Archives at: http://news.gmane.org/gmane.user-groups.linux.delhi http://www.mail-archive.com/ilugd@lists.linux-delhi.org/
