IETF Logo Mail Archive

Re: [DNSOP] Terminology: "primary master"

Joe Abley <jabley@hopcount.ca> Thu, 23 November 2017 18:34 UTC

Return-Path: <jabley@hopcount.ca>
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 40D07129480 for <dnsop@ietfa.amsl.com>; Thu, 23 Nov 2017 10:34:58 -0800 (PST)
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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hopcount.ca
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 LwxBlzBGFQjI for <dnsop@ietfa.amsl.com>; Thu, 23 Nov 2017 10:34:57 -0800 (PST)
Received: from mail-lf0-x22a.google.com (mail-lf0-x22a.google.com [IPv6:2a00:1450:4010:c07::22a]) (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 CD11E126C3D for <dnsop@ietf.org>; Thu, 23 Nov 2017 10:34:56 -0800 (PST)
Received: by mail-lf0-x22a.google.com with SMTP id c188so15446845lfd.5 for <dnsop@ietf.org>; Thu, 23 Nov 2017 10:34:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=from:mime-version:references:in-reply-to:date:message-id:subject:to :cc; bh=/r8EGT758toF+86Y87Zo9sa2tOezgerkla9jzO35LVE=; b=ZELCs6PcedMCfz74JEekg0EAanbfeOLnCGmbTt1ITeCTVfuySr18W/qN0/0+bHvOLo WxfoDzqtNDCSN+sDxGFUwWPsMC2pFjAQTiLFl3f0w1Td4neoJ1hWsGwJxLWdRud0rqCc vTHjyL2lcMpHjxEWj1GPAV8KUjrO9Y4lDX8/g=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:references:in-reply-to:date :message-id:subject:to:cc; bh=/r8EGT758toF+86Y87Zo9sa2tOezgerkla9jzO35LVE=; b=gDspguMYRyhdJVj3BI9pLrfHWL610yQkZ+dtekXbxfKDkvPROYNwS5AkIxQQBtbBbh JCoCVbA0C+Lr3myAxWpM7p/L3SNdtdrYoGRkSHau373yfaa7p2S7paiNvC0r072Rk2dp 2SWGzEVklNyF+c/rc7DEpW+I2Bwwg0e7XRq973VWZtxcHhAoLUng0mCBn7VgmLM9XdEM XgaYHMC5+tE6aYTEz4mDfHncGlYwLk/xRLo/77jENP1R6VrWEKvGJTPV18UxLfDKvPs4 r4gpIplrF1jhZOxcpesj/BUhVdxu26+LgGW5goNh6N4auESvTk3U8c7+ZQcwM6IzuH+O UXwQ==
X-Gm-Message-State: AJaThX5nFrcGu41o24F7MHnPhK7tG7RsQn13DvAA7ZTP/b47tvgmNwzm AasZFpBuVd27OX7zcZBq7doEmOWGcxhfr5foPj99Vg==
X-Google-Smtp-Source: AGs4zMbEtBFtoAIso5G1zTEzFk77mTNwn+sCfsrWmssvb1IZ+SZQ97gPB6n3V4ED4cnRhjiJebURnYSuLPfCH52tWfk=
X-Received: by 10.46.116.9 with SMTP id p9mr7951378ljc.28.1511462094988; Thu, 23 Nov 2017 10:34:54 -0800 (PST)
From: Joe Abley <jabley@hopcount.ca>
Mime-Version: 1.0 (1.0)
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>
In-Reply-To: <alpine.DEB.2.11.1711231740240.4416@grey.csi.cam.ac.uk>
Date: Thu, 23 Nov 2017 13:34:53 -0500
Message-ID: <5562271920774233970@unknownmsgid>
To: Tony Finch <dot@dotat.at>
Cc: Havard Eidnes <he@uninett.no>, "dnsop@ietf.org" <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="089e0827bc8c4379cf055eaab1a0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/ByDLIyJJ5MA8ucbenkEFnI70f-Q>
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:34:58 -0000

On Nov 23, 2017, at 12:44, Tony Finch <dot@dotat.at> wrote:


Joe Abley <jabley@hopcount.ca> wrote:


In that sense the idea of using a single master (which I think is

implied by "primary master" and a name published in a single MNAME

field) is defensibly archaic.


It's quite difficult to have multiple masters and DNSSEC and coherent
copies of the zone from all masters - i.e. more effort than just spinning
up parallel instances of BIND or Knot in automatic signing mode.


Note that I wasn't talking about multiple signers; I was talking about
(from the perspective of one particular slave) having multiple masters
available to serve precisely the same zone.

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.


Joe

v2.23.0 | Report a Bug | By Email