Re: [dhcwg] DDNS-DHCP [6]: Relationship between DNS TTL and DHCP lease length

Ted Lemon <mellon@fugue.com> Thu, 19 June 2003 21:26 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 RAA19392 for <dhcwg-archive@odin.ietf.org>; Thu, 19 Jun 2003 17:26:35 -0400 (EDT)
Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5JLQ8w04809 for dhcwg-archive@odin.ietf.org; Thu, 19 Jun 2003 17:26:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19T6v2-0001FU-3G for dhcwg-web-archive@optimus.ietf.org; Thu, 19 Jun 2003 17:26:08 -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 RAA19356 for <dhcwg-web-archive@ietf.org>; Thu, 19 Jun 2003 17:26:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19T6si-0003Xf-00 for dhcwg-web-archive@ietf.org; Thu, 19 Jun 2003 17:23:45 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19T6si-0003Xc-00 for dhcwg-web-archive@ietf.org; Thu, 19 Jun 2003 17:23:44 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19T6uv-0001Eg-MA; Thu, 19 Jun 2003 17:26:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19T6jy-0000XL-4A for dhcwg@optimus.ietf.org; Thu, 19 Jun 2003 17:14:42 -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 RAA18840 for <dhcwg@ietf.org>; Thu, 19 Jun 2003 17:14:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19T6hf-0003Q9-00 for dhcwg@ietf.org; Thu, 19 Jun 2003 17:12:19 -0400
Received: from toccata.fugue.com ([204.152.186.142]) by ietf-mx with esmtp (Exim 4.12) id 19T6he-0003Q6-00 for dhcwg@ietf.org; Thu, 19 Jun 2003 17:12:18 -0400
Received: from depa.dmes.org (dsl093-187-232.chi2.dsl.speakeasy.net [66.93.187.232]) by toccata.fugue.com (Postfix) with ESMTP id 1AA4E1B2003; Thu, 19 Jun 2003 16:13:08 -0500 (CDT)
From: Ted Lemon <mellon@fugue.com>
To: Robert Elz <kre@munnari.OZ.AU>
Subject: Re: [dhcwg] DDNS-DHCP [6]: Relationship between DNS TTL and DHCP lease length
Date: Thu, 19 Jun 2003 12:40:56 -0500
User-Agent: KMail/1.5
References: <4.3.2.7.2.20030618091029.00b76578@funnel.cisco.com> <14436.1056021556@munnari.OZ.AU>
In-Reply-To: <14436.1056021556@munnari.OZ.AU>
Cc: dhcwg@ietf.org, namedroppers@ops.ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200306191240.56057.mellon@fugue.com>
Content-Transfer-Encoding: 7bit
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>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

On Thursday 19 June 2003 06:19, Robert Elz wrote:
> That is, reworded, to make sure my understanding is correct, the
> problem to be avoided is having a name referring to an address that
> is now to be assigned to a different name ?
>
> Who cares?

Let's say machine X has an SMTP listener, and machine Y also has an SMTP 
listener.   Machine X gets an IP address, Z, from the DHCP server.   Then the 
owner of Machine X wanders away, leaving the lease active.   The lease 
expires, and then machine Y gets the address.   But there is still an A 
record for machine X pointing at IP address Z.   So now, machine Q connects 
to Z because of that A record, and tries to drop mail for X on Y.   Y will 
either bounce it immediately, or bounce it after it notices that the A record 
for X is pointing at it.   So we'd really like it if the time that the A 
record goes away and the time that the lease goes away are fairly close 
together, so that the chances of this happening are slim.

Of course, I would say that this is a broken configuration anyway - you really 
want to use protocols that verify who they're talking to if you have a mobile 
computer.   But that's the basis for caring about this sort of thing, and 
while I don't think we can completely solve the problem, it's worth setting 
things up to minimize the damage that occurs in cases like this.


_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg