IETF Logo Mail Archive

Re: [Resolverless-dns] Paper on Resolver-less DNS

Paul Vixie <paul@redbarn.org> Tue, 20 August 2019 07:05 UTC

Return-Path: <paul@redbarn.org>
X-Original-To: resolverless-dns@ietfa.amsl.com
Delivered-To: resolverless-dns@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1035F1208C4 for <resolverless-dns@ietfa.amsl.com>; Tue, 20 Aug 2019 00:05:07 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] 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 IlPTwKZf5B2W for <resolverless-dns@ietfa.amsl.com>; Tue, 20 Aug 2019 00:05:05 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [24.104.150.213]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BFFE11208EE for <resolverless-dns@ietf.org>; Tue, 20 Aug 2019 00:05:05 -0700 (PDT)
Received: from linux-9daj.localnet (vixp1.redbarn.org [24.104.150.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id B4311892E8; Tue, 20 Aug 2019 07:05:05 +0000 (UTC)
From: Paul Vixie <paul@redbarn.org>
To: resolverless-dns@ietf.org
Cc: John Levine <johnl@taugh.com>, ericorth@google.com
Date: Tue, 20 Aug 2019 07:04:50 +0000
Message-ID: <3636215.4jS6DqXcel@linux-9daj>
Organization: none
In-Reply-To: <20190819170749.5AEF588004D@ary.qy>
References: <20190819170749.5AEF588004D@ary.qy>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/resolverless-dns/8sCQDu1G0pxYdAmlHogVYg_MK3s>
Subject: Re: [Resolverless-dns] Paper on Resolver-less DNS
X-BeenThere: resolverless-dns@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Resolverless DNS <resolverless-dns.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/resolverless-dns>, <mailto:resolverless-dns-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/resolverless-dns/>
List-Post: <mailto:resolverless-dns@ietf.org>
List-Help: <mailto:resolverless-dns-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/resolverless-dns>, <mailto:resolverless-dns-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Aug 2019 07:05:11 -0000

On Monday, 19 August 2019 17:07:49 UTC John Levine wrote:
> In article <CAMOjQcFmqs-s19nd+i-
oeuq4+8zdWVihj6=oGnXC+YL50LxAtg@mail.gmail.com> you write:
> >But that could still be very valuable.  If (and this is a big if) many
> >recursive resolvers use this mechanism to state whether or not they do
> >significant filtering, then for those that report that they do not, this
> >becomes a strong signal to clients that resolverless DNS will not bypass
> >any filtering.
> 
> I'm scratching my head trying to figure out why I would want to
> configure my DNS resolver to tell random malware and PII stealing apps
> what my filtering policy is.

you mustn't, of course. but, anyone who is capable of asking your local RDNS a 
question should also be capable of finding out, reliably, that there _is_ 
policy, so that they can shut down any DoH or resolverless logic they may 
have.

-- 
Paul

v2.23.0 | Report a Bug | By Email