IETF Logo Mail Archive

Re: [DNSOP] Terminology question: split DNS

Bob Harold <rharolde@umich.edu> Mon, 19 March 2018 18:05 UTC

Return-Path: <rharolde@umich.edu>
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 E54C7127369 for <dnsop@ietfa.amsl.com>; Mon, 19 Mar 2018 11:05:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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=umich.edu
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 ODDpUHlCPyZx for <dnsop@ietfa.amsl.com>; Mon, 19 Mar 2018 11:05:48 -0700 (PDT)
Received: from mail-lf0-x230.google.com (mail-lf0-x230.google.com [IPv6:2a00:1450:4010:c07::230]) (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 76F42126C25 for <dnsop@ietf.org>; Mon, 19 Mar 2018 11:05:48 -0700 (PDT)
Received: by mail-lf0-x230.google.com with SMTP id a22-v6so26836872lfg.9 for <dnsop@ietf.org>; Mon, 19 Mar 2018 11:05:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umich.edu; s=google-2016-06-03; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=uvwMV1X78LKDLbQwKNR/Qk5mz1DosDX4enZGwJmfoKM=; b=W1vlRzLkc2BdS0rl4B4lHlD+D+hji/RIpfotFmtuO8ITrn01IdAWn0DcF5/KRDwNTq PK5VSz6Y+M+4pgW+83HI7Poc0pTSEi/w5Wg1fZfSl5DO2cfD1F2eEl0acDnFs9Ts9HcG vt8uHSy2eKpjzcs0lBS0K2eRBhT2jLQVE10NS43R0A7oUJmMYHr0ZEI/zwxOQ5t5kxfC NhgiKMBBdpp0EuWQdoVW3iBwyfkyjgfo2wOXTvAVcFuVdPhON9gvHaQMk6wQNjrh0hkc Xuhwd4M4n7cVk+xo6tltJU+LQ9T7vURMjemsuNSY56J8FSjeAsAuiggRcJ+ujNrwJYqH lRlQ==
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=uvwMV1X78LKDLbQwKNR/Qk5mz1DosDX4enZGwJmfoKM=; b=jBFmxzhLRQ3TqUzq4gWP4bnk5Nf7lajeQP+sf8b0L6k3HvqyQfCsuvYKBzMAefNgkA c4EpiwBs1hk0hkllhDLrTRJOSIchTvzSK+bAbd5gjA6a7S0oc5bDXCYGG8quoR/9/TzK hUf+GAh3cYahpTFPHyai6KnLyyP686qJPi6Wk3rMJceX15ccOUA5pR3Q9vqmKrHSJY/l QqelDe5NuvccO/DYIPtE+7hbeoWGS5EoRTWxIQkGiThHmYB/UiJUZvJ+NP/sXIG4iaFw NC4vNDqnv6eIwxduMy/Bt6IntK9+FKPvjXcA+SDCCT60d9N6hOrqZEtSU4yLWAlxyGXc oREA==
X-Gm-Message-State: AElRT7EIxB4HOvHegfeeMdeVqrGwuw7I/FsJaL6mVngFapVq1ND1ke2+ DJvV9v74no5nGiDf+7ucHrvm6r8OKHbURklALfBtyg==
X-Google-Smtp-Source: AG47ELubG4FNMCps6JCTjt0qmRtXhqUWh0DLCWv/O9uWNfyJUW2MI7G23t/d2j51eKp0/YbJe+0jHenDZjEyR0BeEtM=
X-Received: by 10.46.87.72 with SMTP id r8mr8868523ljd.93.1521482746510; Mon, 19 Mar 2018 11:05:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.46.47.14 with HTTP; Mon, 19 Mar 2018 11:05:45 -0700 (PDT)
In-Reply-To: <CALZ3u+a9o1g0ZTkGjqWwfyV9phovEgu6Linp137yvM=JHSnj-A@mail.gmail.com>
References: <3D490CA8-0733-47AD-A088-113B1116B207@vpnc.org> <CALZ3u+a9o1g0ZTkGjqWwfyV9phovEgu6Linp137yvM=JHSnj-A@mail.gmail.com>
From: Bob Harold <rharolde@umich.edu>
Date: Mon, 19 Mar 2018 14:05:45 -0400
Message-ID: <CA+nkc8DrHTVkbPJDEGksnoN3e-DQtKV1=owOA5pLAUWG+depzw@mail.gmail.com>
To: Artyom Gavrichenkov <ximaera@gmail.com>
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, dnsop <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="f403045f8918a363800567c7ce68"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/1Jup2TMRXoV8D_VGnVpxdrprAgQ>
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:05:52 -0000

On Mon, Mar 19, 2018 at 2:00 PM, Artyom Gavrichenkov <ximaera@gmail.com>
wrote:

> On Mon, Mar 19, 2018 at 5:47 PM, Paul Hoffman <paul.hoffman@vpnc.org>
> wrote:
> > [..] 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."
>
> IP v. being whatever, 4 or 6, there's a bunch of reasons there's
> virtually no correspondence between a given FQDN and a given IP
> address nowadays. E.g. CDNs.
>
>
>
I think the key part is:
   "different answers depending on the source of the query."

In practice this is done by using either different DNS servers (or
processes), or multiple "views" in a DNS configuration.
(Is "view" in BIND called something else in other software?)

-- 
Bob Harold

v2.23.0 | Report a Bug | By Email