Re: [DNSOP] unrelated name server name recommendation

Shumon Huque <shuque@gmail.com> Tue, 05 March 2024 02:42 UTC

Return-Path: <shuque@gmail.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 0F73CC17C8BA for <dnsop@ietfa.amsl.com>; Mon, 4 Mar 2024 18:42:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 gx7nimVp0bN9 for <dnsop@ietfa.amsl.com>; Mon, 4 Mar 2024 18:41:57 -0800 (PST)
Received: from mail-oa1-x32.google.com (mail-oa1-x32.google.com [IPv6:2001:4860:4864:20::32]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C1E31C180B7F for <dnsop@ietf.org>; Mon, 4 Mar 2024 18:41:57 -0800 (PST)
Received: by mail-oa1-x32.google.com with SMTP id 586e51a60fabf-22034c323a3so2463108fac.0 for <dnsop@ietf.org>; Mon, 04 Mar 2024 18:41:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1709606516; x=1710211316; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=Vyrh8DMkEDeCQUAaHewaAuD/k+ylPR4+7n/zRvpOHyE=; b=RYQBDsrSGhwofv3UH9KuOH5byAJcu+rEW8w2lR+UyC7A6s0i+4wG0BhuGnHGeDW1H2 gCGA64+vQe73nbq3vZDXPYwaeaME1d7R/rjked6KQF54ig4lgCWD4rCnaMSW778qA4ns yvRPzCHjHqAEQvykxbqe47wfdfghka8K+J6ittBv3HPUbmYF3lr0+EehmHvP+Goe0rPr 1Weo+PQEJDZNF9yRGpEjjSAZ1q71sU/ITqrbwBUuR35+BBbAoeUtxCbUsb24Q6y8k6qh 8f9uFZPTxUoA+X0bG7igi1Tb55eTVZ4Wj+xbJpa2hyDSX9/9dfzZUu+i/eW67S9EnFyv GVZQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1709606516; x=1710211316; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=Vyrh8DMkEDeCQUAaHewaAuD/k+ylPR4+7n/zRvpOHyE=; b=OnYN3nOxX1u/7uS9XLahg/MyJqAFUOJB+r1C4itRPxHGqMdEQDh0E7QgFZenE7s3tU wZqX8769bHnxlG+3XkRKq6dSyAzaj3hYd52crGWehrje2ckGrXDLzrBGgGSV2s04SWsg btIxmW95mj4RrEjUpWquk1NGR6SJGfzmmh5XcOhh0LZP0q5Qt0BZ657k2WFcfhpATtK0 fUlUypQIFGx3/tNjQz2WXGYxW+kea3bQtD/Yjdkq+BLelmEKdUQ9+p8goRXMomz9oP52 Pi9/iG387igQ59XBYBbx2Bo7R/dRGRc7JDUfLgEuu60xGXJXR8/AWNdekHKa8WzaCxlo GE3w==
X-Gm-Message-State: AOJu0YwoLbEZL/iZK/2mGW0lZ/CWVQ5Oljd7lPN2QVYLV0ldt1wooJV7 wPt9xr0hMu36+r+M8vowQ6/OCX0aDIZCT89K753V+9HMzugXyEocSAxpNcb+HRqs2Tn2eKYUqNR ocdTxPwBwgwPnTamdUtvYo1Sf+UhSVCH6
X-Google-Smtp-Source: AGHT+IF64svDGujhNAypeV7aff7mdnsa84ar1YW/7Deofh8yLPJ1uzULPB51c88/EI/q8yPM51xofPTtx23leXYYbo4=
X-Received: by 2002:a05:6870:c391:b0:21e:bd75:1947 with SMTP id g17-20020a056870c39100b0021ebd751947mr536705oao.59.1709606516447; Mon, 04 Mar 2024 18:41:56 -0800 (PST)
MIME-Version: 1.0
References: <20240304.133402.1564724475540797830.fujiwara@jprs.co.jp>
In-Reply-To: <20240304.133402.1564724475540797830.fujiwara@jprs.co.jp>
From: Shumon Huque <shuque@gmail.com>
Date: Mon, 04 Mar 2024 21:41:45 -0500
Message-ID: <CAHPuVdX8qeAwoo1JwYcVq8pLYUpDiipZ4Uua-i6yNVsDvQaJsA@mail.gmail.com>
To: Kazunori Fujiwara <fujiwara@jprs.co.jp>
Cc: dnsop@ietf.org
Content-Type: multipart/alternative; boundary="0000000000001e60040612e0c9d6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/MJZAKSB0-w-rssIKKea8AlfpAq8>
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: Tue, 05 Mar 2024 02:42:03 -0000

On Sun, Mar 3, 2024 at 11:34 PM Kazunori Fujiwara <fujiwara@jprs.co.jp>
wrote:

> dnsop WG,
>
> "unrelated" (or, previosly called as out-of-bailiwick) name server names
> are
> necessary for DNS hosting providers.
>

Fujiwara-san, I have to nitpick your very first statement above.

Many DNS providers do offer the ability to pick "vanity" or "custom"
nameserver
names, which their customers can use to deploy in-domain nameservers. This
could be because the customer really does want to make DNS resolution
efficient.
But it could be for other reasons (branding, or some other perceived
security reason).
My employer uses such features extensively.

This is not simply the customer pointing their own names at the provider's
DNS server
addresses. This is a contract with the provider that they will maintain
that association
and won't change the IP addresses from under them (the "going stale"
problem) without
advance notice and coordination.

I think I agree with your general goal, but as others have remarked, there
is no way to
enforce this, so at best this could be a recommendation.

Shumon.