Re: [DNSOP] [Ext] RCODE and CNAME chain

Edward Lewis <> Wed, 05 April 2017 13:34 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id A3053129405 for <>; Wed, 5 Apr 2017 06:34:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id gJKV435u3_KN for <>; Wed, 5 Apr 2017 06:34:37 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 6B570127863 for <>; Wed, 5 Apr 2017 06:34:37 -0700 (PDT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1178.4; Wed, 5 Apr 2017 06:34:35 -0700
Received: from ([]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([]) with mapi id 15.00.1178.000; Wed, 5 Apr 2017 06:34:35 -0700
From: Edward Lewis <>
To: Mukund Sivaraman <>, "" <>
Thread-Topic: [Ext] [DNSOP] RCODE and CNAME chain
Thread-Index: AQHSrc+er/xSohK310Ock8cYx7x68KG2+WQA
Date: Wed, 5 Apr 2017 13:34:34 +0000
Message-ID: <>
References: <20170405054338.GA15831@jurassic>
In-Reply-To: <20170405054338.GA15831@jurassic>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
user-agent: Microsoft-MacOutlook/f.20.0.170309
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3574229674_411370557"
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [DNSOP] [Ext] RCODE and CNAME chain
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 05 Apr 2017 13:34:40 -0000

On 4/5/17, 01:43, "DNSOP on behalf of Mukund Sivaraman" < on behalf of> wrote:

>It seems BIND currently returns NXDOMAIN in this case, and the change in
>behavior between looking-into-other-zones and
>not-looking-into-other-zones in the nameserver algorithm caused a system
>test failure, hence the question.

I don't think there is one right answer.  There may be a more efficient answer (in terms of some metric).  The goal of the RFCs was interoperability, keep that in mind.

You allude above to an implementation changing its behavior (answering from all available data vs. sticking to one zone).  This is not something that is explicitly dealt with in the original RFCs, perhaps in later ones.  Both choices have merit, have downsides, still the two are interoperable.  As far as the protocol matters, either is a valid choice, and one that influences whether the query in question results in NOERROR/CNAME chain or NXDOMAIN.

In this case, I think you don't need to worry about the querier.  Rules seem to be explicit about caching responses here.

If anything, make sure your test script is accurate.  (Back in the day of DNSSEC protocol/code development, 1 out of 3 times DNSSEC had a protocol bug, 1 out of 3 times it was a software bug, and 1 out of 3 times everything was right but the tester - me - was expecting the wrong result.)