Re: [DNSOP] Fwd: New Version Notification for draft-muks-dnsop-dns-thundering-herd-00.txt

Paul Vixie <> Fri, 26 June 2020 01:02 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 541E63A10B7 for <>; Thu, 25 Jun 2020 18:02:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id SwhuwoiDitNr for <>; Thu, 25 Jun 2020 18:02:54 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 47A5A3A1046 for <>; Thu, 25 Jun 2020 18:02:54 -0700 (PDT)
Received: from linux-9daj.localnet ( []) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (1024 bits) server-digest SHA256) (Client did not present a certificate) by (Postfix) with ESMTPSA id C164EB0588; Fri, 26 Jun 2020 01:02:51 +0000 (UTC)
From: Paul Vixie <>
To: Mukund Sivaraman <>,
Cc: Cricket Liu <>,, Paul Wouters <>
Date: Fri, 26 Jun 2020 01:02:51 +0000
Message-ID: <1825040.HPJnnLGoiM@linux-9daj>
Organization: none
In-Reply-To: <>
References: <> <> <>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <>
Subject: Re: [DNSOP] Fwd: New Version Notification for draft-muks-dnsop-dns-thundering-herd-00.txt
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 26 Jun 2020 01:02:55 -0000

On Thursday, 25 June 2020 18:29:03 UTC Paul Wouters wrote:
> On Thu, 25 Jun 2020, Mukund Sivaraman wrote:
> > For whoever is interested, this is a description of a pattern of queries
> > noticed at busy public resolvers that has led to issues in at least 4
> > different sites in the last 2 months.
> > 
> > The current revision is a work in progress. We are still developing some
> > mitigations for NIOS, and some more introductory text also has to be
> > added.
> I would add a more explicit section on using prefetching of frequently
> asked queries, which mitigates (eliminates) the period when an answer is not
> available in the cache.

i'm sorry in advance for anybody who is now hearing this for the 100th time.

please don't pre-fetch. feel free to pre-discard; TTL is a maximum, and if you 
want to randomly subtract from TTL upon every reuse, you'll remain compliant. 
if the data turns out to be important it'll return. but prospective pre-fetch 
means you may be creating network load for no purpose -- the data may not come 
back again, or if it does, it may have changed, in which case you don't want 
the stale stuff that pre-fetch would have brought you.

this solves the thundering herd problem but without creating new problems. the 
goal is de-synchronization. random subtractions to TTL in cache accomplishes