Re: [ntpwg] [dhcwg] Re: Network Time Protocol (NTP) OptionsforDHCPv6

Ted Lemon <Ted.Lemon@nominum.com> Tue, 27 November 2007 23:09 UTC

Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ix9Ys-0005JK-Om; Tue, 27 Nov 2007 18:09:50 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ix9Yq-0005EY-PX for dhcwg@ietf.org; Tue, 27 Nov 2007 18:09:49 -0500
Received: from exprod7og103.obsmtp.com ([64.18.2.159]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ix9Yp-0002lW-Rj for dhcwg@ietf.org; Tue, 27 Nov 2007 18:09:48 -0500
Received: from source ([81.200.64.181]) (using TLSv1) by exprod7ob103.postini.com ([64.18.6.12]) with SMTP; Tue, 27 Nov 2007 15:09:42 PST
Received: from mail.nominum.com (mail.nominum.com [81.200.64.186]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by shell-ng.nominum.com (Postfix) with ESMTP id EAA8A56884; Tue, 27 Nov 2007 15:09:41 -0800 (PST) (envelope-from mellon@nominum.com)
X-Spam-Status: No, hits=0.0 required=8.4 tests=CUSTOM_RULE_FROM: ALLOW,TOTAL_SCORE: 0.000
X-Spam-Level:
Received: from [10.71.0.243] ([12.4.29.2]) (authenticated user mellon@nominum.com) by mail.nominum.com (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits)); Tue, 27 Nov 2007 15:09:40 -0800
Message-Id: <BFF6FCB9-231F-4EB8-B4CB-3FCD1F673FFA@nominum.com>
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "David L. Mills" <mills@udel.edu>
In-Reply-To: <474C855F.6080609@udel.edu>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v915)
Subject: Re: [ntpwg] [dhcwg] Re: Network Time Protocol (NTP) OptionsforDHCPv6
Date: Tue, 27 Nov 2007 18:09:40 -0500
References: <200711260009.lAQ092va059077@drugs.dv.isc.org> <EF06E977-C3D9-4EDF-A126-6CD888BA8F36@fugue.com> <014d01c82fc6$6b1ecd70$6401a8c0@tsg1> <5C093633-A256-4059-AA10-1800F62F522A@fugue.com> <017901c82fd4$9cad3b70$6401a8c0@tsg1> <E0F01D6C-3FB6-4150-9722-32CFF3079327@fugue.com> <018501c82fd7$9ff707e0$6401a8c0@tsg1> <A6BDB3D6-4CDA-4BC1-ADF0-1845E539DD4C@fugue.com> <474A521A.2090905@ntp.org> <EB79E4A4-9DC7-4C86-8CB7-96920EAD579A@fugue.com> <p06240803c37171dcd41c@[192.168.1.135]> <474C855F.6080609@udel.edu>
X-Mailer: Apple Mail (2.915)
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: "ntpwg@lists.ntp.org" <ntpwg@lists.ntp.org>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
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>
Errors-To: dhcwg-bounces@ietf.org

On Nov 27, 2007, at 4:00 PM, David L. Mills wrote:
> If the DHCP server followed that advice, it would
> occasionally re-resolve the name and pass the new IP address to its
> clients.  It is not at all clear that this advice is followed in the  
> real
> world.

It is followed, actually.   E.g., the Nominum DHCP server (DCS) just  
looks the name up every time, under the assumption that the caching  
name server is going to perform better than any ad hoc resolver we  
might stuff into the DHCP server.   The ISC DHCP server caches names  
for an hour - a decision I made when caching name servers weren't as  
good as they are now, and when I was a lot more naive about DNS than I  
am now.  I can't speak for the other vendors, so you'd have to ask  
them, but I'd be really surprised if they didn't do the same thing -  
if you cache the value, you have to cache it some/where/ - it's not  
quite the same as when a server looks up an address in the DNS so that  
it can connect to that address.

I don't know what SOHO routers do, in general - it would be  
interesting to investigate.



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