[72650] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

RE: VeriSign's rapid DNS updates in .com/.net

daemon@ATHENA.MIT.EDU (Ray Plzak)
Thu Jul 22 05:47:00 2004

From: "Ray Plzak" <plzak@arin.net>
To: <nanog@merit.edu>
Date: Thu, 22 Jul 2004 05:46:01 -0400
In-Reply-To: <20040722071146.GC5422@reifa.local>
Errors-To: owner-nanog-outgoing@merit.edu


Good point!  You can reduce TTLs to such a point that the servers will
become preoccupied with doing something other than providing answers.

Ray

> -----Original Message-----
> From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu] On Behalf Of
> Daniel Karrenberg
> Sent: Thursday, July 22, 2004 3:12 AM
> To: Matt Larson
> Cc: nanog@merit.edu
> Subject: Re: VeriSign's rapid DNS updates in .com/.net
> 
> 
> Matt, others,
> 
> I am a quite concerned about these zone update speed improvements
> because they are likely to result in considerable pressure to reduce
> TTLs **throughout the DNS** for little to no good reason.
> 
> It will not be long before the marketeers will discover that they do not
> deliver what they (implicitly) promise to customers in case of **changes
> and removals** rather than just additions to a zone.
> 
> Reducing TTLs across the board will be the obvious *soloution*.
> 
> Yet, the DNS architecture is built around effective caching!
> 
> Are we sure that the DNS as a whole will remain operational when
> (not if) this happens in a significant way?
> 
> Can we still mitigate that trend by education of marketeers and users?
> 
> Daniel


home help back first fref pref prev next nref lref last post