Re: [DNSOP] Terminology question: split DNS

Artyom Gavrichenkov <ximaera@gmail.com> Mon, 19 March 2018 18:10 UTC

Return-Path: <ximaera@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 F0FEE12946D for <dnsop@ietfa.amsl.com>; Mon, 19 Mar 2018 11:10:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MrkDiz3Y_HKy for <dnsop@ietfa.amsl.com>; Mon, 19 Mar 2018 11:10:16 -0700 (PDT)
Received: from mail-ua0-x22f.google.com (mail-ua0-x22f.google.com [IPv6:2607:f8b0:400c:c08::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 48B10126C25 for <dnsop@ietf.org>; Mon, 19 Mar 2018 11:10:16 -0700 (PDT)
Received: by mail-ua0-x22f.google.com with SMTP id x17so5039346uaj.12 for <dnsop@ietf.org>; Mon, 19 Mar 2018 11:10:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=9r5ReEDdVW9XZ/51iCZknwR32Yvyl1WkLrfCiNqHCSA=; b=A3vs+qTqcirTBOtCu1Le3UwBWlDo0baC4FFq+YrbNcTSjKrA7/u4DfGthtcDTlJlTB VDGHM3zlQKRwLt9xN1odMi4SUlYAoWUEib36yoCo0nKWLh9V6h4HPS/rJLESpICk9MLo KwDSjN3Zc1V/F/BlGcAvmHvRVDWl0ZQemA+Eg2a3ZvvJ4ADWBVD9xST2JB3wgTstKOkW bO4P/zsET4CFfqYagA/neMbGUYvHdpefg3s1RxcpIoWapme4pY6tzpaICR4h41E79s76 nZKSeOxIpDZhQl06xNx2BsR4Kjhd6ynl0VhbgaqOGgfTuf+EyOt7MHi44uhfLc33Gi9P 5OeA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=9r5ReEDdVW9XZ/51iCZknwR32Yvyl1WkLrfCiNqHCSA=; b=AeDscRgW6Y0OAy3isBdJkM7DTBs1SsYemxgeGKPf+ycrhptN0Kr+fW0UdfyIXnUCPp 2TgHHxjArlXy+sbfmRvgh5ZTjkzPBog2dFKudDb3cpkGJyMteSMYvq71Tq4QWxNIEXej idSUlm/hduSMVyTyTqUQ8UlSBJyicO9Mj3juWa17u5BOavu78xSVecknlDodN12k4rkM +mzUG1QUEFMZOn8KTryHCbzGBVT6C+KjKrJt/7ZH66q50D7yeW4gyN/c501zeEN8Dh3y JjUKoocCLnfSOYV8r8HBg5pqLJHj5LaWvzZOuqc0pL7Jwz3Q9JU/KHTE42E6kmEXUUbB aTZA==
X-Gm-Message-State: AElRT7FioBu7nR18goHGbbVTMyhazgpEKOUWKqJfb+53poZhCeJvFAbZ sLzwIku2iIoS0vwKMIWRKItj/nJWpy1OiO/IKtM=
X-Google-Smtp-Source: AG47ELsTKcDRXJSXBS2mrpbnLrzax1dh65FQ8q/DaGpHNVcUOgVKdUBokLW7M6Le9m6xxqEXufKqEQybmoBFOlQHrgw=
X-Received: by 10.176.95.217 with SMTP id g25mr7386170uaj.186.1521483015176; Mon, 19 Mar 2018 11:10:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.159.57.111 with HTTP; Mon, 19 Mar 2018 11:09:54 -0700 (PDT)
In-Reply-To: <CA+nkc8DrHTVkbPJDEGksnoN3e-DQtKV1=owOA5pLAUWG+depzw@mail.gmail.com>
References: <3D490CA8-0733-47AD-A088-113B1116B207@vpnc.org> <CALZ3u+a9o1g0ZTkGjqWwfyV9phovEgu6Linp137yvM=JHSnj-A@mail.gmail.com> <CA+nkc8DrHTVkbPJDEGksnoN3e-DQtKV1=owOA5pLAUWG+depzw@mail.gmail.com>
From: Artyom Gavrichenkov <ximaera@gmail.com>
Date: Mon, 19 Mar 2018 18:09:54 +0000
Message-ID: <CALZ3u+bs+uDm16UiHp6fAF+EyrA9FBcbvYhRap76Wb6MCz_vOg@mail.gmail.com>
To: Bob Harold <rharolde@umich.edu>
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, dnsop <dnsop@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/aLTPACyczwNCfMpqynizOKYf0Jc>
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 18:10:18 -0000

On Mon, Mar 19, 2018 at 6:05 PM, Bob Harold <rharolde@umich.edu>; wrote:
> In practice this is done by using either different DNS servers (or
> processes), or multiple "views" in a DNS configuration.

Another issue here is that, for some enterprises at least, there's no
single "internal network" anymore. There are different network scopes
(_sometimes_ nested) ranging from "formally internal but treated as
almost external" to "air gap-separated DMZ", with different policies,
including different DNS policies.

My second thought (personally) is that there might be a reason to just
bury the "split DNS" definition whatsoever and to just define a
"multi-horizon DNS", where a "horizon" is defined by a company's
policy and _usually_ depends on the source IP address of a query
(there may be exceptions).

| Artyom Gavrichenkov
| gpg: 2deb 97b1 0a3c 151d b67f 1ee5 00e7 94bc 4d08 9191
| mailto: ximaera@gmail.com
| fb: ximaera
| telegram: xima_era
| skype: xima_era
| tel. no: +7 916 515 49 58