Re: [DNSOP] Minimum viable ANAME

Paul Vixie <> Sun, 04 November 2018 08:01 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 073E1127133 for <>; Sun, 4 Nov 2018 01:01:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id e8aLDbScFiwk for <>; Sun, 4 Nov 2018 01:01:30 -0700 (PDT)
Received: from ( [IPv6:2001:559:8000:cd::5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E647D130E08 for <>; Sun, 4 Nov 2018 01:01:30 -0700 (PDT)
Received: from [] (unknown []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by (Postfix) with ESMTPSA id 88EED892C6; Sun, 4 Nov 2018 08:01:29 +0000 (UTC)
Message-ID: <>
Date: Sun, 04 Nov 2018 01:01:27 -0700
From: Paul Vixie <>
User-Agent: Postbox 5.0.25 (Windows/20180328)
MIME-Version: 1.0
To: Ray Bellis <>
References: <20180919201401.8E0C220051382A@ary.qy> <> <20180920061343.GA754@jurassic> <> <> <> <> <>
In-Reply-To: <>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <>
Subject: Re: [DNSOP] Minimum viable ANAME
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: Sun, 04 Nov 2018 08:01:32 -0000

Ray Bellis wrote:
> On 04/11/2018 08:05, Ray Bellis wrote:
>> AFAIK, BIND does not currently do this.  That said, MarkA has a patch
>> that supports it, so we do know it's possible.
> Correction - BIND *does* do this, but only for address records that are
> already in the cache. If the AAAA for the target is in the cache, but
> the A record isn't, that's all you'll get.

that's all we need. it's all we do for MX and NS additional data, too.

> Mark's patch forces BIND to pre-fill the cache with the A and AAAA
> records for the SRV target before replying.

that would be a mistake. we are hitting for average here not power -- 
the behaviour to optimize for is whatever's most common. if the SRV is 
used, the AAAA or A RRsets will be fetched, and thus cached. if the SRV 
is only used once, that caching effort will be wasted. if the SRV is 
used many times, then the dominant use case will be that the additional 
data is found in cache because the client caused this to be so.

P Vixie