Re: [DNSOP] Adding more example configurations to draft-ietf-dnsop-7706bis

Ray Bellis <ray@bellis.me.uk> Fri, 26 October 2018 11:33 UTC

Return-Path: <ray@bellis.me.uk>
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 D9B4A130DDA for <dnsop@ietfa.amsl.com>; Fri, 26 Oct 2018 04:33:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 Sj-39AReEvK7 for <dnsop@ietfa.amsl.com>; Fri, 26 Oct 2018 04:33:25 -0700 (PDT)
Received: from hydrogen.portfast.net (hydrogen.portfast.net [188.246.200.2]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 938371200D7 for <dnsop@ietf.org>; Fri, 26 Oct 2018 04:33:25 -0700 (PDT)
Received: from [88.212.170.147] (port=58921 helo=rays-mbp.local) by hydrogen.portfast.net ([188.246.200.2]:465) with esmtpsa (fixed_plain:ray@bellis.me.uk) (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) id 1gG0Mk-0007qX-Eg (Exim 4.72) for dnsop@ietf.org (return-path <ray@bellis.me.uk>); Fri, 26 Oct 2018 12:33:22 +0100
To: dnsop@ietf.org
References: <47597960-3D11-4007-947D-19DBC7AF2BAC@icann.org> <75129a2d-8f91-48ca-dc27-7d6dfde685e0@bellis.me.uk> <alpine.DEB.2.20.1810261210150.24450@grey.csi.cam.ac.uk>
From: Ray Bellis <ray@bellis.me.uk>
Message-ID: <a1b6b9c4-6d0c-d277-2b9b-575880bc1c14@bellis.me.uk>
Date: Fri, 26 Oct 2018 12:33:23 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <alpine.DEB.2.20.1810261210150.24450@grey.csi.cam.ac.uk>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/kZRwi8DwMoaECGIDQqIsMnUaT5I>
Subject: Re: [DNSOP] Adding more example configurations to draft-ietf-dnsop-7706bis
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 26 Oct 2018 11:33:28 -0000

On 26/10/2018 12:14, Tony Finch wrote:

> It's basically the same as the examples in RFC 7706, but you use the other
> host's address instead of 127.12.12.12.
The BIND configuration becomes *much* simpler if you don't try to put
(validating) recursion and root zone copy into the same server.

You just need:

zone "." {
  type static-stub;
  server-addresses { x.x.x.x };
};

> RFC 7706 even says,
> 
>  The examples here use a loopback address of 127.12.12.12, but typical
>  installations will use 127.0.0.1.  The different address is used in
>  order to emphasize that the root server does not need to be on the
>  device at "localhost".

The 7706-bis text changes that to say:

   The examples here use a loopback address of 127.12.12.12, but typical
   installations will use 127.0.0.1.  The different address is used in
   order to emphasize that the root server does not need to be on the
   device at the name "localhost" which is often locally served as
   127.0.0.1.

My reading of this is that "the device" referred to is still "the local
device", not "a n other device".  I think the text is just trying to say
"just because it's on loopback doesn't require that it be *called*
localhost".

Ray