Re: [DNSOP] Terminology: "primary master"

Paul Vixie <paul@redbarn.org> Thu, 23 November 2017 18:49 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 7F2FB12948A for <dnsop@ietfa.amsl.com>; Thu, 23 Nov 2017 10:49:02 -0800 (PST)
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, 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 RqSodjOKbc1m for <dnsop@ietfa.amsl.com>; Thu, 23 Nov 2017 10:49:01 -0800 (PST)
Received: from family.redbarn.org (family.redbarn.org [IPv6:2001:559:8000:cd::5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6CEAF129453 for <dnsop@ietf.org>; Thu, 23 Nov 2017 10:49:01 -0800 (PST)
Received: from [172.31.98.14] (unknown [4.35.165.51]) (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 E192F61FA2; Thu, 23 Nov 2017 18:48:59 +0000 (UTC)
Message-ID: <5A171818.4080507@redbarn.org>
Date: Thu, 23 Nov 2017 10:48:56 -0800
From: Paul Vixie <paul@redbarn.org>
User-Agent: Postbox 5.0.20 (Windows/20171012)
MIME-Version: 1.0
To: Joe Abley <jabley@hopcount.ca>
CC: "dnsop@ietf.org" <dnsop@ietf.org>
References: <20171123.121943.1115399549648860645.he@uninett.no> <34F896BC-B044-4E46-AC60-8562A8BE782F@hopcount.ca> <alpine.DEB.2.11.1711231740240.4416@grey.csi.cam.ac.uk> <5562271920774233970@unknownmsgid>
In-Reply-To: <5562271920774233970@unknownmsgid>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/U1wUg_iiqTZBMZu8_ymaOX41v7M>
Subject: Re: [DNSOP] Terminology: "primary master"
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: Thu, 23 Nov 2017 18:49:02 -0000


Joe Abley wrote:
> ...
>
> Feeding a large array of slaves (eg hundreds, including individual
> members if clusters) with large numbers of zones from a single master
> doesn't scale very well.

when i had to do this i fed 100 from one or two, where the two were HA 
using non-DNS tech such as NFS or sql mirroring. then i've fed 1000 from 
each of those hundred, choosing one as primary and one as backup.

if you have a better way, using extant, open technology, to reach 
100,000 zxfr/ixfr clients with secure coherent zone content with minimal 
delay, i'd like to hear more.

when i had to feed hundreds of zones to large populations, i used MZ 
(see http://family.redbarn.org/~vixie/mz.pdf and perhaps also 
dotat.at/prog/nsnotifyd/metazone.5.pdf).

if you have a better way, using extant, open technology, to propagate a 
moderate to large and dynamic catalogue of zones toward a cooperating 
set of secondary servers, i'd like to hear more.

-- 
P Vixie