Re: [DNSOP] Terminology question: split DNS

Paul Vixie <paul@redbarn.org> Mon, 19 March 2018 17:54 UTC

Return-Path: <paul@redbarn.org>
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 37CDF127333 for <dnsop@ietfa.amsl.com>; Mon, 19 Mar 2018 10:54:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nFwLDba1GruN for <dnsop@ietfa.amsl.com>; Mon, 19 Mar 2018 10:54:50 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [24.104.150.213]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 77478126C25 for <dnsop@ietf.org>; Mon, 19 Mar 2018 10:54:50 -0700 (PDT)
Received: from [192.168.9.206] (5-226-86-5.static.ip.netia.com.pl [5.226.86.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id C1C2F7594C; Mon, 19 Mar 2018 17:54:49 +0000 (UTC)
Message-ID: <5AAFF968.10407@redbarn.org>
Date: Mon, 19 Mar 2018 10:54:48 -0700
From: Paul Vixie <paul@redbarn.org>
User-Agent: Postbox 5.0.24 (Windows/20180302)
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
CC: dnsop <dnsop@ietf.org>
References: <3D490CA8-0733-47AD-A088-113B1116B207@vpnc.org>
In-Reply-To: <3D490CA8-0733-47AD-A088-113B1116B207@vpnc.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/FAzX7lHtGHOkObP8snSOeJctFyc>
Subject: Re: [DNSOP] Terminology question: split DNS
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
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, 19 Mar 2018 17:54:52 -0000


Paul Hoffman wrote:
> Some folks had reservations about the current definition of "split
> DNS": "Where a corporate network serves up partly or completely
> different DNS inside and outside its firewall. There are many
> possible variants on this; the basic point is that the correspondence
> between a given FQDN (fully qualified domain name) and a given IPv4
> address is no longer universal and stable over long periods." (Quoted
> from <xref target="RFC2775"/>, Section 3.8)
>
> What would the WG like for this definition?

my only qualm is that A and AAAA RR's are not the only things that are 
usually not the same when DNS is split in this way. MX, NS, SRV, and 
likely a dozen others, and DNSSEC signatures and keys, can also differ.

it should be called split-horizon DNS not split-DNS, to highlight the 
fact that it's the same zone name in an entirely separate DNS namespace.

-- 
P Vixie