Re: [DNSOP] Root server tar pitting? Is there a better way?

bert hubert <bert.hubert@netherlabs.nl> Mon, 16 May 2016 21:45 UTC

Return-Path: <bert.hubert@powerdns.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80C8112D538 for <dnsop@ietfa.amsl.com>; Mon, 16 May 2016 14:45:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.325
X-Spam-Level:
X-Spam-Status: No, score=-3.325 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RP_MATCHES_RCVD=-1.426] 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 Drl7Zx_SROMb for <dnsop@ietfa.amsl.com>; Mon, 16 May 2016 14:45:08 -0700 (PDT)
Received: from tmpmail.powerdns.com (tmpmail.powerdns.com [128.199.32.142]) by ietfa.amsl.com (Postfix) with ESMTP id 17AD712B043 for <dnsop@ietf.org>; Mon, 16 May 2016 14:45:08 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tmpmail.powerdns.com (Postfix) with ESMTP id 848E460095; Mon, 16 May 2016 17:45:07 -0400 (EDT)
Received: from tmpmail.powerdns.com ([127.0.0.1]) by localhost (tmpmail.powerdns.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1VUZZdnR8kuu; Mon, 16 May 2016 17:45:07 -0400 (EDT)
Received: from server.ds9a.nl (unknown [IPv6:2001:470:1f15:bba::42]) by tmpmail.powerdns.com (Postfix) with ESMTP id 1EA086008A; Mon, 16 May 2016 17:45:07 -0400 (EDT)
Received: by server.ds9a.nl (Postfix, from userid 1000) id 150AEAC1CCB; Mon, 16 May 2016 23:45:07 +0200 (CEST)
Date: Mon, 16 May 2016 23:45:07 +0200
From: bert hubert <bert.hubert@netherlabs.nl>
To: "Wessels, Duane" <dwessels@verisign.com>
Message-ID: <20160516214507.GA28128@server.ds9a.nl>
References: <44FFEAA9-7579-47E9-A5AF-5C0E1B720634@opendns.com> <29A70833-47CA-4371-8150-9C7AB16A0877@verisign.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <29A70833-47CA-4371-8150-9C7AB16A0877@verisign.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/r_m6BLBvgJ3ReF-unpZsS2x5SMg>
Cc: "dnsop@ietf.org" <dnsop@ietf.org>, Brian Somers <bsomers@opendns.com>
Subject: Re: [DNSOP] Root server tar pitting? Is there a better way?
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 May 2016 21:45:09 -0000

On Mon, May 16, 2016 at 09:34:17PM +0000, Wessels, Duane wrote:
> Hi Brian,
> 
> I think what you're suggesting has already been proposed.  See https://datatracker.ietf.org/doc/draft-fujiwara-dnsop-nsec-aggressiveuse/ and https://datatracker.ietf.org/doc/draft-wkumari-dnsop-cheese-shop/

It is in fact something you can do today. Some of the largest PowerDNS
Recursor sites in the world run with 'root-nx-trust' enabled:

"If set, an NXDOMAIN from the root-servers will serve as a blanket NXDOMAIN
for the entire TLD the query belonged to. The effect of this is far fewer
queries to the root-servers."

This after f-root had enabled RRL slightly too aggressively on some nodes.

We just tested this setting against the "owned Ubiquity" attack and after a
thousand queries or so traffic to the roots dropped off to almost zero.

        Bert