Re: [DNSOP] unrelated name server name recommendation
Paul Wouters <paul@nohats.ca> Mon, 04 March 2024 19:14 UTC
Return-Path: <paul@nohats.ca>
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 558C9C180B61 for <dnsop@ietfa.amsl.com>; Mon, 4 Mar 2024 11:14:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.104
X-Spam-Level:
X-Spam-Status: No, score=-7.104 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
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 hQ7C-Bjo7va4 for <dnsop@ietfa.amsl.com>; Mon, 4 Mar 2024 11:14:32 -0800 (PST)
Received: from mx.nohats.ca (mx.nohats.ca [IPv6:2a03:6000:1004:1::85]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C5F1C1654F3 for <dnsop@ietf.org>; Mon, 4 Mar 2024 11:14:31 -0800 (PST)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 4TpT0507X6zCW9; Mon, 4 Mar 2024 20:14:29 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1709579669; bh=dHjyUu2A7w660OhcAsEKr+vuZHMy+rKoBGsHVDg5l/I=; h=From:Subject:Date:References:Cc:In-Reply-To:To; b=SL8fTC4F2LiL7aTiKriGd4yTMm0NhRje7uGFrd0N2LVqqYWkf24iV9r5XttLx6IGN NlHBp89/naRpkJ/tmLkjc0PyA7l/GcQ/tnmj7ExRu5Ugno6iFIVflbgOV1CKUr1dWQ tvff/Qns7q+pnKW93ukqpRXYvChnn5ezN1xVYCbA=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id gX2R4iuxOinZ; Mon, 4 Mar 2024 20:14:27 +0100 (CET)
Received: from bofh.nohats.ca (bofh.nohats.ca [193.110.157.194]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Mon, 4 Mar 2024 20:14:27 +0100 (CET)
Received: from smtpclient.apple (unknown [193.110.157.208]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by bofh.nohats.ca (Postfix) with ESMTPSA id 9CD341179826; Mon, 4 Mar 2024 14:14:20 -0500 (EST)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Paul Wouters <paul@nohats.ca>
Mime-Version: 1.0 (1.0)
Date: Mon, 04 Mar 2024 14:14:10 -0500
Message-Id: <BE280DCA-104F-49AB-B28E-9C703E65E213@nohats.ca>
References: <978e2792-1cdf-b33e-532f-83356a5f1ff2@redbarn.org>
Cc: dnsop@ietf.org
In-Reply-To: <978e2792-1cdf-b33e-532f-83356a5f1ff2@redbarn.org>
To: Paul Vixie <paul=40redbarn.org@dmarc.ietf.org>
X-Mailer: iPhone Mail (21D61)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/nfVM67gvZpNGyFJfPx-28mUvbWA>
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 19:14:37 -0000
On Mar 4, 2024, at 14:04, Paul Vixie <paul=40redbarn.org@dmarc.ietf.org> wrote: > > > > this means a zone will always be reachable through at least one in-zone data path (name server name and associated address records.) the result would be that a full resolver would never have to pause its current lookup while searching for address records matching an out-of-zone name server name. > > i think it's a solid recommendation, 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, the ISP has to talk to the registrant to fix things at their registry. I can promise you those in-domain name servers will quickly become very unreliable. Paul
- [DNSOP] unrelated name server name recommendation Kazunori Fujiwara
- Re: [DNSOP] unrelated name server name recommenda… Ben Schwartz
- Re: [DNSOP] unrelated name server name recommenda… Paul Vixie
- Re: [DNSOP] unrelated name server name recommenda… Paul Wouters
- Re: [DNSOP] unrelated name server name recommenda… Peter Thomassen
- Re: [DNSOP] unrelated name server name recommenda… Wessels, Duane
- Re: [DNSOP] unrelated name server name recommenda… Jim Reid
- Re: [DNSOP] unrelated name server name recommenda… Shumon Huque
- Re: [DNSOP] unrelated name server name recommenda… Kazunori Fujiwara
- Re: [DNSOP] unrelated name server name recommenda… Paul Vixie