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

Mukund Sivaraman <> Fri, 15 June 2018 19:52 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id BBDD8130E40 for <>; Fri, 15 Jun 2018 12:52:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.901
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 ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Vdm2z4vKYWaJ for <>; Fri, 15 Jun 2018 12:52:41 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id CF85D130DBE for <>; Fri, 15 Jun 2018 12:52:40 -0700 (PDT)
Received: from jurassic (unknown []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPSA id C9AFE32C0A28; Fri, 15 Jun 2018 19:52:38 +0000 (UTC)
Date: Sat, 16 Jun 2018 01:22:32 +0530
From: Mukund Sivaraman <>
To: Bob Harold <>
Cc: Shumon Huque <>, IETF DNSOP WG <>, Andrew Sullivan <>
Message-ID: <20180615195232.GA5926@jurassic>
References: <> <> <> <>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <>
User-Agent: Mutt/1.9.2 (2017-12-15)
Archived-At: <>
Subject: Re: [DNSOP] BCP on rrset ordering for round-robin? Also head's up on bind 9.12 bug (sorting rrsets by default)
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: IETF DNSOP WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 15 Jun 2018 19:52:43 -0000

On Fri, Jun 15, 2018 at 02:38:00PM -0400, Bob Harold wrote:
> Round-robin is a documented feature that many applications use.  Removing
> it from DNS resolvers, and then having to add it to a much larger number of
> applications, does not seem like a good trade-off.

The _default_ in BIND 9.12 was changed from order random to order
none. It seems to be missing from the release notes by mistake, but the
administrator manual mentions what the default is:

	    By default, records are returned in indeterminate but
            consistent order (see <command>none</command> above).

As before, an admin can configure it to any of {fixed, random, cyclic,
none} per class/type/domain, in named.conf. See the section "RRset
Ordering" in the administror manual.

No sorting functionality was removed. The default was changed.