Re: [DNSOP] DNS names for local networks - not only home residental networks ...

Tony Finch <dot@dotat.at> Wed, 06 September 2017 18:48 UTC

Return-Path: <dot@dotat.at>
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 0BB0F13294B for <dnsop@ietfa.amsl.com>; Wed, 6 Sep 2017 11:48:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 CvzGrxoyKYHM for <dnsop@ietfa.amsl.com>; Wed, 6 Sep 2017 11:48:14 -0700 (PDT)
Received: from ppsw-32.csi.cam.ac.uk (ppsw-32.csi.cam.ac.uk [131.111.8.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 33F211321A2 for <dnsop@ietf.org>; Wed, 6 Sep 2017 11:48:14 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://help.uis.cam.ac.uk/email-scanner-virus
Received: from grey.csi.cam.ac.uk ([131.111.57.57]:35076) by ppsw-32.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.136]:25) with esmtps (TLSv1:ECDHE-RSA-AES256-SHA:256) id 1dpfMw-000N0Q-39 (Exim 4.89) (return-path <dot@dotat.at>); Wed, 06 Sep 2017 19:48:11 +0100
Date: Wed, 06 Sep 2017 19:48:10 +0100
From: Tony Finch <dot@dotat.at>
To: Paul Vixie <paul@redbarn.org>
cc: dnsop@ietf.org
In-Reply-To: <20170906172257.wr57ralm56pzdrbr@mx4.yitter.info>
Message-ID: <alpine.DEB.2.11.1709061900240.2628@grey.csi.cam.ac.uk>
References: <150428805872.6417.9525310755360551475@ietfa.amsl.com> <59A9B760.2060209@mathemainzel.info> <alpine.LRH.2.21.1709011556280.12556@bofh.nohats.ca> <59A9BD75.5010408@mathemainzel.info> <alpine.LRH.2.21.1709011612470.12556@bofh.nohats.ca> <CAHw9_iKKDFj4SJtpxV=egNB0D=jkBFnQ68N5kOgUBFieexvsTA@mail.gmail.com> <59AB67A2.3000008@redbarn.org> <20170906172257.wr57ralm56pzdrbr@mx4.yitter.info>
User-Agent: Alpine 2.11 (DEB 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/42Hj7T1H28dOSl4fP-Jcyv8F8oE>
Subject: Re: [DNSOP] DNS names for local networks - not only home residental networks ...
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: Wed, 06 Sep 2017 18:48:16 -0000

Paul Vixie <paul@redbarn.org> wrote:
>
> we do not have well defined automation for making local names work when
> the internet connection is down. at a very modest level of necessary and
> inevitable complexity, one's own in-perimeter recursive servers can't
> find one's own in-perimeter authority servers. so if your internet
> connection goes down, then way more stuff becomes effectively
> unreachable than what's on the far side of the disconnection point.
>
> mark andrews faced disconnections of this kind as a daily part of his
> work about 30 years ago when he developed the "stub zone" feature and
> contributed it to BIND4. but we have yet to automate it.

This won't address the deeper problems that you outlined, but...

It occurs to me that this could be made a lot simpler with the right
flavour of metazone / catalogue zone.

On our site we encourage those running BIND to secondary our local zones,
but it's horrible to configure and there's a lot of manualarity to
co-ordinate delegation changes. But it has nice resilience and performance
properties.

However I'm doubtful that it's worth trying to make it possible to
automatically discover a catalogue zone for the local domains on the local
network...

Forwarding to our recursive servers is a lot simpler to configure and has
easier support for DNSSEC validation. Sadly DNSSEC reintroduces the
external dependency problem, but serve-stale should mitigate that when
our recursive servers support it.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/  -  I xn--zr8h punycode
Biscay: Westerly or northwesterly 3 or 4, occasionally 5 in north. Moderate,
occasionally rough in north. Mainly fair. Good.