Re: [dhcwg] DDNS-DHCP [6]: Relationship between DNS TTL and DHCP lease length
"D. J. Bernstein" <djb@cr.yp.to> Wed, 25 June 2003 15:03 UTC
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13756 for <dhcwg-archive@odin.ietf.org>; Wed, 25 Jun 2003 11:03:04 -0400 (EDT)
Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5PF2cl24844 for dhcwg-archive@odin.ietf.org; Wed, 25 Jun 2003 11:02:38 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VBnC-0006Sd-OF for dhcwg-web-archive@optimus.ietf.org; Wed, 25 Jun 2003 11:02:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13670 for <dhcwg-web-archive@ietf.org>; Wed, 25 Jun 2003 11:02:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19VBmv-0004GS-00 for dhcwg-web-archive@ietf.org; Wed, 25 Jun 2003 11:02:21 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19VBmp-0004GO-00 for dhcwg-web-archive@ietf.org; Wed, 25 Jun 2003 11:02:15 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VBma-0006OQ-LA; Wed, 25 Jun 2003 11:02:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UtRs-0002Va-DQ for dhcwg@optimus.ietf.org; Tue, 24 Jun 2003 15:27:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06047 for <dhcwg@ietf.org>; Tue, 24 Jun 2003 15:27:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19UtRc-0006LN-00 for dhcwg@ietf.org; Tue, 24 Jun 2003 15:27:08 -0400
Received: from stoneport.math.uic.edu ([131.193.178.160]) by ietf-mx with smtp (Exim 4.12) id 19UtRQ-0006L3-00 for dhcwg@ietf.org; Tue, 24 Jun 2003 15:26:57 -0400
Received: (qmail 79373 invoked by uid 1016); 24 Jun 2003 19:26:53 -0000
Date: Tue, 24 Jun 2003 19:26:53 -0000
Message-ID: <20030624192653.79372.qmail@cr.yp.to>
Automatic-Legal-Notices: See http://cr.yp.to/mailcopyright.html.
From: "D. J. Bernstein" <djb@cr.yp.to>
To: namedroppers@ops.ietf.org, dhcwg@ietf.org
Subject: Re: [dhcwg] DDNS-DHCP [6]: Relationship between DNS TTL and DHCP lease length
References: <20030623174016.B97901396A@sa.vix.com> <Pine.LNX.4.44.0306241204050.10688-100000@x22.ripe.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Id: <dhcwg.ietf.org>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
Bruce Campbell writes: > So... if a record is due to expire in 1500 seconds, and you know that the > slave 'should' transfer the zone again via axfr in 1300 seconds (via SOA > values), you will merrily supply a 2 second TTL on said records Correct. Yes, short TTLs cause minor increases in the frequency of DNS lookups, but long TTLs cause administrative headaches. If the next AXFR is delayed, the old data will stick around longer than it should. > Still, when new records are created, you have to propagate the information > outwards. Rsync, AXFR and IXFR are all unsuitable for this in a > frequently changing environment due to their associated overhead. Actually, rsync and tinydns-data can make any number of updates to a multiple-megabyte database in well under a second on a typical computer. ---D. J. Bernstein, Associate Professor, Department of Mathematics, Statistics, and Computer Science, University of Illinois at Chicago _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- Re: [dhcwg] DDNS-DHCP [6]: Relationship between D… Ralph Droms
- Re: [dhcwg] DDNS-DHCP [6]: Relationship between D… Robert Elz
- Re: [dhcwg] DDNS-DHCP [6]: Relationship between D… Ted Lemon
- Re: [dhcwg] DDNS-DHCP [6]: Relationship between D… Ralph Droms
- Re: [dhcwg] DDNS-DHCP [6]: Relationship between D… Robert Elz
- Re: [dhcwg] DDNS-DHCP [6]: Relationship between D… Mark Stapp
- Re: [dhcwg] DDNS-DHCP [6]: Relationship between D… Ted Lemon
- Re: [dhcwg] DDNS-DHCP [6]: Relationship between D… Edward Lewis
- Re: [dhcwg] DDNS-DHCP [6]: Relationship between D… D. J. Bernstein
- Re: [dhcwg] DDNS-DHCP [6]: Relationship between D… Michael Richardson
- Re: [dhcwg] DDNS-DHCP [6]: Relationship between D… Robert Elz
- Re: [dhcwg] DDNS-DHCP [6]: Relationship between D… D. J. Bernstein
- Re: [dhcwg] DDNS-DHCP [6]: Relationship between D… Ted Lemon
- Re: [dhcwg] DDNS-DHCP [6]: Relationship between D… Bruce Campbell
- Re: [dhcwg] DDNS-DHCP [6]: Relationship between D… D. J. Bernstein
- Re: [dhcwg] DDNS-DHCP [6]: Relationship between D… Paul Vixie
- Re: [dhcwg] DDNS-DHCP [6]: Relationship between D… Paul Vixie
- Re: [dhcwg] DDNS-DHCP [6]: Relationship between D… Bruce Campbell
- Re: [dhcwg] DDNS-DHCP [6]: Relationship between D… D. J. Bernstein