IETF Logo Mail Archive

[dbound] NXDomain (was: Re: [dmarc-ietf] Fwd: New Version Notification for draft-dcrocker-dns-perimeter-00.txt)

Dave Crocker <dhc@dcrocker.net> Sat, 06 April 2019 12:36 UTC

Return-Path: <dhc@dcrocker.net>
X-Original-To: dbound@ietfa.amsl.com
Delivered-To: dbound@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECE1212001A for <dbound@ietfa.amsl.com>; Sat, 6 Apr 2019 05:36:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.301
X-Spam-Level:
X-Spam-Status: No, score=-1.301 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dcrocker.net
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 fJKFWLQEyQYT for <dbound@ietfa.amsl.com>; Sat, 6 Apr 2019 05:36:49 -0700 (PDT)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (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 6C0BB120049 for <dbound@ietf.org>; Sat, 6 Apr 2019 05:36:49 -0700 (PDT)
Received: from [192.168.1.85] (108-226-162-63.lightspeed.sntcca.sbcglobal.net [108.226.162.63]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1.1) with ESMTP id x36CcX5J008602 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for <dbound@ietf.org>; Sat, 6 Apr 2019 05:38:33 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1554554314; bh=/u4Zd8WkNQJwhjDBOkS0VasvgUEfumJEziXQT4pIDjE=; h=Subject:To:References:Reply-To:From:Date:In-Reply-To:From; b=d8CxB5zIQU+lTYckLpTzqwJgsr4bQX4JSH72MU+p5CMzi4UTKY4MuvFaVxu0eu4g6 cIUy71XZyNArKq3e7l/56CBHWLqMppwuUt2Yi7xdDqPKQoeJokLtqPzM9tgs6RX96u 3TNv0ocXEHyf2Qt1uZZoDKNZ5gODb9UtIUGH7DZE=
To: dbound@ietf.org
References: <20190403175820.8391420115F376@ary.qy> <2445c121-f77b-0fa2-ca6a-402479abb5a7@dcrocker.net> <alpine.OSX.2.21.1904031430270.21189@ary.qy> <7e61b445-3844-f769-6a59-16fa396388d0@dcrocker.net> <alpine.OSX.2.21.1904031459480.21189@ary.qy> <AFE01C0B-E47E-4D4E-B60C-FA0810BBE8F8@gmail.com> <310cc611-e1f0-2fbb-6efe-9d266869d025@dcrocker.net> <alpine.OSX.2.21.1904032056230.22661@ary.qy> <da2b2c91-8b9f-1254-d159-997bb77c1a9e@bbiw.net> <alpine.OSX.2.21.1904032126480.22887@ary.qy> <a5f53382-b1f5-bf9b-aa3e-1fc2e93786f4@bbiw.net> <alpine.OSX.2.21.1904032148150.22920@ary.qy>
Reply-To: dcrocker@bbiw.net
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <acb079bc-53d4-780b-2f1c-98072159e7aa@dcrocker.net>
Date: Sat, 06 Apr 2019 05:36:40 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <alpine.OSX.2.21.1904032148150.22920@ary.qy>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dbound/_gHKXWAFf4EzJfgYJssGqPpsRYQ>
Subject: [dbound] NXDomain (was: Re: [dmarc-ietf] Fwd: New Version Notification for draft-dcrocker-dns-perimeter-00.txt)
X-BeenThere: dbound@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DNS tree bounds <dbound.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dbound>, <mailto:dbound-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dbound/>
List-Post: <mailto:dbound@ietf.org>
List-Help: <mailto:dbound-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dbound>, <mailto:dbound-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Apr 2019 12:36:51 -0000

>      if you ask for _perim.a.b.c.tld, and there is only _perim.c.tld,
> the DNS response will be an NXDOMAIN and I don't think that DNS clients 
> expect to find additional records in an NXDOMAIN response.


So indeed, this was an interesting point.

However from what I can tell, including Additional information in an 
NXDomain response is entirely legal, albeit certainly unusual.

My understanding is that it's likely careful use of a resolver library 
can retrieve the Additional information.  Some calls won't get it; 
others probably will.

The guidance for making this work is that it's seeking to emulate DNS 
wildcard behavior, through cooperative behavior by both the resolver and 
the authoritative server.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

v2.23.0 | Report a Bug | By Email