Re: [DNSOP] RCODE and CNAME chain

[Jan Včelák <[e-mail]>]

Hello,

sorry for resurrecting this thread, but this really caught my attention.

On Wed, Apr 5, 2017 at 9:03 AM, Peter van Dijk wrote:
> On 5 Apr 2017, at 7:43, Mukund Sivaraman wrote:
>> Evan just pointed out a case due to a system test failure that is
>> interesting.. it's not clear what the behavior should be in this case,
>> so please discuss:
>>
>> There's a nameserver that's authoritative for 2 zones example.org. and
>> example.com.
>>
>> In the example.org. zone, foo.example.org. is CNAME to bar.example.com.
>>
>> In the example.com. zone, the name bar.example.com. doesn't exist (NXDOMAIN).
>>
>> A query for "foo.example.org./A" is answered by the nameserver. It adds
>> the foo.example.org. CNAME bar.example.com. in the answer section, and
>> then, following RFC 1034 4.3.2. 3.(a.), sets the QNAME to
>> "bar.example.com" and looks into the "example.com" zone for
>> "bar.example.com.". It is not found.
>>
>> The question is: what is the expected reply RCODE for this?
>>
>> 1. Is it NOERROR (0) because there is an answer section with the CNAME?
>>
>> 2. Is it NXDOMAIN (3) because the CNAME target was not found?
>
> NXDOMAIN is correct. The text on this on 103x is a bit weak but 2308 2.1 clarifies this.
>

I actually think NOERROR is correct. The target of the CNAME
(bar.example.com) is not in the bailiwick of the zone (example.org)
So the authoritative server should stop processing the CNAME chain at
this point and send the response with RCODE=NOERROR.

Or can we at least agree that both RCODEs are correct? :-)

Jan