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

Viktor Dukhovni <> Wed, 04 September 2019 14:50 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4794E12023E for <>; Wed, 4 Sep 2019 07:50:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 HhOqDb6rHHL0 for <>; Wed, 4 Sep 2019 07:50:31 -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 6EA96120169 for <>; Wed, 4 Sep 2019 07:50:19 -0700 (PDT)
Received: by (Postfix, from userid 1001) id 49D2429CF96; Wed, 4 Sep 2019 10:50:18 -0400 (EDT)
Date: Wed, 04 Sep 2019 10:50:18 -0400
From: Viktor Dukhovni <>
Message-ID: <>
References: <> <> <> <> <> <> <> <> <> <>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <>
User-Agent: Mutt/1.12.1 (2019-06-15)
Archived-At: <>
Subject: Re: [Resolverless-dns] Paper on Resolver-less DNS
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Resolverless DNS <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 04 Sep 2019 14:50:36 -0000

On Wed, Sep 04, 2019 at 03:51:55PM +0200, Erik Sy wrote:

> > What else could it mean?
> Note, that the retrieval of a popular website requires on average
> connections to about 20 different hostnames. Thus, if the first
> connection to an average website provides you the DNS records for the
> remaining 19 hostnames then using resolver-less DNS can save up to 19
> traditional DNS lookups.

A more conservative "scope" for any such address hints would be to
limit them to just to the display of the current "location" (web
page).  When the browser navigates to a new page, any such cache
should be flushed.  This should include navigation via links on the
page.  Only the retrieval of resources needed to display the current
page would then make use any returned addresses.

Many users re-use existing tabs to navigate to new sites independent
of the one previously displayed in the tab.

Some of the concerns I have raised are ameliorated if the scope of
the returned addresses is limited to just the page being displayed.
That way, one perhaps gets faster loading of images, Javascript
(and advertisements, if not blocked).

That said, browsers do DNS lookups in parallel, and the user's
resolver will often already have the answers in its cache.  Is the
resulting reduction in latency really worth the added complexity
and potential risks?