Re: [DNSOP] DoH interaction, sortlist Re: BCP on rrset ordering for round-robin? Also head's up on bind 9.12 bug (sorting rrsets by default)

Philip Homburg <pch-dnsop-3@u-1.phicoh.com> Sat, 16 June 2018 12:04 UTC

Return-Path: <pch-bCE2691D2@u-1.phicoh.com>
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 6164A130DEB for <dnsop@ietfa.amsl.com>; Sat, 16 Jun 2018 05:04:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 Lt53Qmyqk9i8 for <dnsop@ietfa.amsl.com>; Sat, 16 Jun 2018 05:04:51 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo6-tun.hq.phicoh.net [IPv6:2001:888:1044:10:2a0:c9ff:fe9f:17a9]) (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 2075A12F1AC for <dnsop@ietf.org>; Sat, 16 Jun 2018 05:04:50 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384) (Smail #157) id m1fU9wl-0000IwC; Sat, 16 Jun 2018 14:04:47 +0200
Message-Id: <m1fU9wl-0000IwC@stereo.hq.phicoh.net>
To: dnsop@ietf.org
Cc: bert hubert <bert.hubert@powerdns.com>
From: Philip Homburg <pch-dnsop-3@u-1.phicoh.com>
Sender: pch-bCE2691D2@u-1.phicoh.com
References: <CAKC-DJimMOtNCSE95kRs6Dy3dC_mxB=8O2WVA7badp8GK2ci-Q@mail.gmail.com> <20180615171231.GF1126@mx4.yitter.info> <20180616055407.GA16195@server.ds9a.nl>
In-reply-to: Your message of "Sat, 16 Jun 2018 07:54:07 +0200 ." <20180616055407.GA16195@server.ds9a.nl>
Date: Sat, 16 Jun 2018 14:04:46 +0200
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/PSQLWkJDkSV8POXJrQ_gkHQkpL8>
Subject: Re: [DNSOP] DoH interaction, sortlist Re: BCP on rrset ordering for round-robin? Also head's up on bind 9.12 bug (sorting rrsets by default)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.26
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: Sat, 16 Jun 2018 12:04:54 -0000

>At that lunch, we could not figure out who originally required such a
>detailed ordering configuration in BIND, and it might be interesting to find
>out.

What I remember from a very long time ago is the following network setup:
- a collection of NFS servers each with multiple ethernet interface cards
  connecting to different subnets
- a collection of NFS clients that would connect to the first address in 
  the returned RRset (i.e. that would not locally sort the RRset)
- a DNS resolver in a completely different subnet that had incomplete knowledge
  of the network. I think bind treated the 'class B' network as a single
  network, not as a collection of /24s.

Without the sortlist feature the DNS resolver had not enough information
to move the best address to the start of the list. And the router was slow
enough that you didn't want NFS traffic to go through the router.