From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-3.3 required=5.0 tests=MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 9775 invoked from network); 24 Aug 2020 22:05:01 -0000 Received: from mother.openwall.net (195.42.179.200) by inbox.vuxu.org with ESMTPUTF8; 24 Aug 2020 22:05:01 -0000 Received: (qmail 30035 invoked by uid 550); 24 Aug 2020 22:04:57 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 30017 invoked from network); 24 Aug 2020 22:04:56 -0000 From: Florian Weimer To: Rich Felker Cc: musl@lists.openwall.com References: <5232EC15-7E60-4D1F-BF3B-C31BFF998C06@rb67.eu> <20200824161646.GH3265@brightrain.aerifal.cx> <20200824164326.GI3265@brightrain.aerifal.cx> <87mu2jycum.fsf@mid.deneb.enyo.de> <20200824213215.GL3265@brightrain.aerifal.cx> Date: Tue, 25 Aug 2020 00:04:44 +0200 In-Reply-To: <20200824213215.GL3265@brightrain.aerifal.cx> (Rich Felker's message of "Mon, 24 Aug 2020 17:32:15 -0400") Message-ID: <87eenvya2r.fsf@mid.deneb.enyo.de> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [musl] Incompatible behaviour of res_query(3) w.r.t. NXDOMAIN * Rich Felker: > On Mon, Aug 24, 2020 at 11:04:49PM +0200, Florian Weimer wrote: >> * Rich Felker: >> >> > Hmm, I think in this case the "better" might be sufficient that we >> > want to keep it and pressure other implementations to change too. A >> > program performing a lookup where the result is NxDomain may very well >> > want to know whether that's an authenticated (by DNSSEC) NxDomain or >> > one in an insecure zone. Returning an error to the caller with no >> > packet contents discards this critical data. >> >> Isn't this the behavior you'd get with res_send? >> >> I think such error translation is precisely the point of the res_query >> convenience function (along with the implicit construction of the >> query packet). > > Does such a distinction exist? Yes, I think so. It's the behavior of the BIND 4 era stub resolver code.