IETF Logo Mail Archive

Re: [Add] Mozilla's DoH resolver policy

Jim Reid <jim@rfc1035.com> Thu, 11 April 2019 09:11 UTC

Return-Path: <jim@rfc1035.com>
X-Original-To: add@ietfa.amsl.com
Delivered-To: add@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CA2B120287 for <add@ietfa.amsl.com>; Thu, 11 Apr 2019 02:11:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
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 GimUeB6x2S6j for <add@ietfa.amsl.com>; Thu, 11 Apr 2019 02:11:24 -0700 (PDT)
Received: from shaun.rfc1035.com (shaun.rfc1035.com [93.186.33.42]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 45D6312028B for <add@ietf.org>; Thu, 11 Apr 2019 02:11:24 -0700 (PDT)
Received: from [172.17.16.14] (unknown [195.70.2.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by shaun.rfc1035.com (Postfix) with ESMTPSA id D9D96242109D; Thu, 11 Apr 2019 09:11:21 +0000 (UTC)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Jim Reid <jim@rfc1035.com>
In-Reply-To: <CACQYfiJa1i2LVgQDcHi_OknmDDKZiaw=++Y6imn34LcPULP3bQ@mail.gmail.com>
Date: Thu, 11 Apr 2019 10:11:20 +0100
Cc: add@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <D5F958D7-A158-4B20-AF4A-FA3CAE33BFC3@rfc1035.com>
References: <297C80CE-F017-4F4A-80E2-79941E8B9E02@icann.org> <b64761dc-dfab-e4e1-4bfb-82d607efa590@riseup.net> <alpine.LRH.2.21.1904101324530.9940@bofh.nohats.ca> <64aeff58-6d68-4c4f-b991-2b2f62d193a0@www.fastmail.com> <90A5C5C4-373C-4B39-80C2-C115CD23CB4D@fl1ger.de> <CACQYfiJa1i2LVgQDcHi_OknmDDKZiaw=++Y6imn34LcPULP3bQ@mail.gmail.com>
To: Valentin Gosu <valentin.gosu@gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/IQpLDgB2ZXBUM3NbOgni776MoP4>
Subject: Re: [Add] Mozilla's DoH resolver policy
X-BeenThere: add@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications Doing DNS <add.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/add>, <mailto:add-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/add/>
List-Post: <mailto:add@ietf.org>
List-Help: <mailto:add-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/add>, <mailto:add-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Apr 2019 09:11:25 -0000


> On 11 Apr 2019, at 10:04, Valentin Gosu <valentin.gosu@gmail.com> wrote:
> 
> Because at the moment a DNSSEC failure response from the DoH server is identical to an NXDOMAIN response, which causes us to fallback to regular DNS anyway.

DNSSEC failures return SERVFAIL (something bad/unrecoverable has happened). That's very different from NXDOMAIN responses (the name/class/qtype doesn't exist). I hope DoH servers don't consider these things to be the same because they're not.

v2.23.0 | Report a Bug | By Email