[89436] in North American Network Operators' Group
RE: DNS TTL adherence
daemon@ATHENA.MIT.EDU (Sharad Agarwal)
Wed Mar 15 23:24:30 2006
Date: Wed, 15 Mar 2006 20:23:08 -0800
In-Reply-To: <E73B77BE9ADCF44BB936593743E85ADD04EA3106@exmsea008.us.wamu.net>
From: "Sharad Agarwal" <Sharad.Agarwal@microsoft.com>
To: <nanog@merit.edu>
Errors-To: owner-nanog@merit.edu
(re-sending because I wasn't on nanog-post)
> For example if we change ip addresses will we need to plan on=20
> 20% traffic at old site on day1, 10% day2, 5%, day3, and so=20
> on...? There are also issues related to proxy servers and=20
> browser caching that are independent of DNS we will need to=20
> quantify to understand full risk. The more data we have will=20
> drive some of our decisions.
You might consider the following paper from IMC 2003: "On the
Responsiveness of DNS-based Network Control" by Jeffrey Pang, Aditya
Akella, Anees Shaikh, Balachander Krishnamurthy, Srinivasan Seshan,
http://www.imconf.net/imc-2004/papers/p21-pang.pdf
It sheds some light on how widely DNS TTLs are adhered to. The CDF
graphs on the 4th page suggest that you should be fairly safe after a
day, though I don't see if the paper specifically states what the
largest recorded violation was.
Sharad.
