nanog mailing list archives
RE: VeriSign's rapid DNS updates in .com/.net
From: Henry Linneweh <hrlinneweh () sbcglobal net>
Date: Thu, 22 Jul 2004 08:50:01 -0700 (PDT)
Before a big panic starts, they can restore it back to the way it was if there is an event of such proportion to totally hoze the entire network or any major portion of it, until they fix any major issue with these changes.... -Henry --- Sam Stickland <sam_ml () spacething org> wrote:
Well, a naive calculation, based on reducing the TTL to 15 mins from 24 hours to match Verisign's new update times, would suggest that the number of queries would increase by (24 * 60) / 15 = 96 times? (or twice that if you factor in for the Nyquist interval). Any there any resources out there there that have information on global DNS statistics? ie. the average TTL currently in use. But I guess it remains to be seen if this will have a knock on effect like that described below. Verisign are only doing this for the nameserver records at present time - it just depends on whether expection for such rapid changes gets pushed on down. Sam On Thu, 22 Jul 2004, Ray Plzak wrote:Good point! You can reduce TTLs to such a pointthat the servers willbecome preoccupied with doing something other thanproviding answers.Ray-----Original Message----- From: owner-nanog () merit edu[mailto:owner-nanog () merit edu] On Behalf OfDaniel 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/.netMatt, others, I am a quite concerned about these zone updatespeed improvementsbecause they are likely to result inconsiderable pressure to reduceTTLs **throughout the DNS** for little to nogood reason.It will not be long before the marketeers willdiscover that they do notdeliver what they (implicitly) promise tocustomers in case of **changesand removals** rather than just additions to azone.Reducing TTLs across the board will be theobvious *soloution*.Yet, the DNS architecture is built aroundeffective caching!Are we sure that the DNS as a whole will remainoperational when(not if) this happens in a significant way? Can we still mitigate that trend by education ofmarketeers and users?Daniel
Current thread:
- Re: VeriSign's rapid DNS updates in .com/.net, (continued)
- Re: VeriSign's rapid DNS updates in .com/.net Mike Lewinski (Jul 10)
- Re: VeriSign's rapid DNS updates in .com/.net David A . Ulevitch (Jul 10)
- Re: VeriSign's rapid DNS updates in .com/.net Suresh Ramasubramanian (Jul 10)
- Re: VeriSign's rapid DNS updates in .com/.net william(at)elan.net (Jul 12)
- Re: VeriSign's rapid DNS updates in .com/.net Daniel Karrenberg (Jul 22)
- RE: VeriSign's rapid DNS updates in .com/.net Ray Plzak (Jul 22)
- RE: VeriSign's rapid DNS updates in .com/.net Sam Stickland (Jul 22)
- RE: VeriSign's rapid DNS updates in .com/.net Stephen J. Wilcox (Jul 22)
- Re: VeriSign's rapid DNS updates in .com/.net Daniel Karrenberg (Jul 22)
- Re: VeriSign's rapid DNS updates in .com/.net william(at)elan.net (Jul 22)
- RE: VeriSign's rapid DNS updates in .com/.net Ray Plzak (Jul 22)
- RE: VeriSign's rapid DNS updates in .com/.net Henry Linneweh (Jul 22)
- RE: VeriSign's rapid DNS updates in .com/.net (fwd from ml) Sam Stickland (Jul 22)
- RE: VeriSign's rapid DNS updates in .com/.net (fwd from ml) Sam Stickland (Jul 22)
- Re: VeriSign's rapid DNS updates in .com/.net Paul Vixie (Jul 22)
- Re: VeriSign's rapid DNS updates in .com/.net Daniel Karrenberg (Jul 22)
- Re: VeriSign's rapid DNS updates in .com/.net Daniel Karrenberg (Jul 22)
- Re: VeriSign's rapid DNS updates in .com/.net Pete Schroebel (Jul 22)
- Re: VeriSign's rapid DNS updates in .com/.net Eric Brunner-Williams in Portland Maine (Jul 22)
- Re: VeriSign's rapid DNS updates in .com/.net Mark Kosters (Jul 22)
- Re: VeriSign's rapid DNS updates in .com/.net Valdis . Kletnieks (Jul 22)
- Re: VeriSign's rapid DNS updates in .com/.net Eric Brunner-Williams in Portland Maine (Jul 22)