Re: [DNSOP] New draft for ALIAS/ANAME type

Tony Finch <> Mon, 03 April 2017 12:11 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7B6D3127601 for <>; Mon, 3 Apr 2017 05:11:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id SbgFHUCiqr7r for <>; Mon, 3 Apr 2017 05:11:01 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 63E2C126BF7 for <>; Mon, 3 Apr 2017 05:11:01 -0700 (PDT)
X-Cam-AntiVirus: no malware found
Received: from ([]:48174) by ( []:25) with esmtps (TLSv1:ECDHE-RSA-AES256-SHA:256) id 1cv0p0-000s6c-ia (Exim 4.89) (return-path <>); Mon, 03 Apr 2017 13:10:58 +0100
Date: Mon, 03 Apr 2017 13:10:58 +0100
From: Tony Finch <>
To: Peter van Dijk <>
In-Reply-To: <>
Message-ID: <>
References: <> <20170330230806.6273.qmail@ary.lan> <> <> <>
User-Agent: Alpine 2.11 (DEB 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Archived-At: <>
Subject: Re: [DNSOP] New draft for ALIAS/ANAME type
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 03 Apr 2017 12:11:03 -0000

Peter van Dijk <> wrote:
> On 31 Mar 2017, at 12:10, Tony Finch wrote:
> >
> > Does the more ambitious version use the NSEC rdata format so that you can
> > have different target names for different alias RR types?
> I got this question some time ago when I was working on ALIAS for PowerDNS.
> Back then I said no, as nobody showed me an actual use case for it and I did
> not like the extra complexity. Today I feel the same way and the upcoming
> draft does not have type bitmaps currently.

That's probably sensible :-)

The vague idea I had was ALIAS A AAAA for your web hosting provider and
ALIAS MX TXT for your mail hosting provider. But the latter isn't actually
very useful, since MX and SPF records have built-in indirection, and TXT
is also used for other purposes (domain authorization, quite frequently in
my experience), and it doesn't cover DKIM or MUA SRV records. And other
scenarios stub their toes in similar ways, e.g. for SIP there's a mess of
SRV records plus NAPTR, and a NAPTR RRset can cover multiple unrelated
protocols and providers.

So I think my conclusion is that ALIAS is both unnecessary and unhelpful
for RRtypes other than A and AAAA.

f.anthony.n.finch  <>  -  I xn--zr8h punycode
Trafalgar: North or northeast 4 or 5, increasing 6 at times. Moderate at first
in east, otherwise rough. Fair. Good.