IETF Logo Mail Archive

Re: [DNSOP] unrelated name server name recommendation

Jim Reid <jim@rfc1035.com> Mon, 04 March 2024 21:10 UTC

Return-Path: <jim@rfc1035.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7413C180B6D for <dnsop@ietfa.amsl.com>; Mon, 4 Mar 2024 13:10:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level:
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 29t3NWHE1FLs for <dnsop@ietfa.amsl.com>; Mon, 4 Mar 2024 13:10:45 -0800 (PST)
Received: from shaun.rfc1035.com (smtp.v6.rfc1035.com [IPv6:2001:4b10:100:7::25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7DAD4C151525 for <dnsop@ietf.org>; Mon, 4 Mar 2024 13:10:42 -0800 (PST)
Received: from smtpclient.apple (212-147-18-59.fix.access.vtx.ch [212.147.18.59]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by shaun.rfc1035.com (Postfix) with ESMTPSA id BD3E32420E4A; Mon, 4 Mar 2024 21:10:37 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.400.31\))
From: Jim Reid <jim@rfc1035.com>
In-Reply-To: <BE280DCA-104F-49AB-B28E-9C703E65E213@nohats.ca>
Date: Mon, 04 Mar 2024 21:10:37 +0000
Cc: Paul Vixie <paul=40redbarn.org@dmarc.ietf.org>, dnsop@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <B493E93D-3764-4622-A1C6-B600EDA97947@rfc1035.com>
References: <978e2792-1cdf-b33e-532f-83356a5f1ff2@redbarn.org> <BE280DCA-104F-49AB-B28E-9C703E65E213@nohats.ca>
To: Paul Wouters <paul@nohats.ca>
X-Mailer: Apple Mail (2.3774.400.31)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/HQDv5lXiMGpRX96tsVEP8gnur2k>
Subject: Re: [DNSOP] unrelated name server name recommendation
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Mar 2024 21:10:47 -0000


> On 4 Mar 2024, at 19:14, Paul Wouters <paul@nohats.ca> wrote:
> 
> It means every registrant, who doesn’t know about DNS, has to create host objects for glue and whenever the ISP changes nameserver names (eg gets bought, sold or merges), or IP address

Er, no. It’ll be the registant’s registrar who will screw this up - not the registrant (who can’t even spell DNS). Besides in most cases, the it’ll be the registrar who looks after that delegation info and also provides DNS service for the registant’s domain name.

v2.23.0 | Report a Bug | By Email