Re: [DNSOP] new ANAME draft: draft-hunt-dnsop-aname-00.txt

"Peter van Dijk" <peter.van.dijk@powerdns.com> Wed, 12 April 2017 19:10 UTC

Return-Path: <peter.van.dijk@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 5A027129571 for <dnsop@ietfa.amsl.com>; Wed, 12 Apr 2017 12:10:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 TAJEWy1DvVnW for <dnsop@ietfa.amsl.com>; Wed, 12 Apr 2017 12:10:25 -0700 (PDT)
Received: from shannon.7bits.nl (shannon.7bits.nl [IPv6:2a01:1b0:202:40::1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6809312EB3A for <dnsop@ietf.org>; Wed, 12 Apr 2017 12:10:22 -0700 (PDT)
Received: from [192.168.137.1] (unknown [82.168.30.10]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: peter) by shannon.7bits.nl (Postfix) with ESMTPSA id EFB06C1B96; Wed, 12 Apr 2017 21:10:20 +0200 (CEST)
From: "Peter van Dijk" <peter.van.dijk@powerdns.com>
To: dnsop <dnsop@ietf.org>
Date: Wed, 12 Apr 2017 21:10:20 +0200
Message-ID: <BCA68541-684C-417F-8B51-3D14D47C3BA1@powerdns.com>
In-Reply-To: <alpine.LRH.2.20.999.1704111147390.8670@bofh.nohats.ca>
References: <20170407181139.GB66383@isc.org> <cc3bbc7a-3f48-2f7f-a3d9-3f752874fc00@redhat.com> <alpine.DEB.2.11.1704111641290.4393@grey.csi.cam.ac.uk> <alpine.LRH.2.20.999.1704111147390.8670@bofh.nohats.ca>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate (1.9.6r5347)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/gRBaFzAJGFPJVL2vc-Xmxeu5Lr0>
Subject: Re: [DNSOP] new ANAME draft: draft-hunt-dnsop-aname-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 12 Apr 2017 19:10:26 -0000

On 11 Apr 2017, at 20:16, Paul Wouters wrote:

> On Tue, 11 Apr 2017, Tony Finch wrote:
>
>> ANAME
>> records are not just for zone apexes. There are lots of other cases 
>> where
>> address records need a different alias target from MX records, or 
>> NAPTR
>> records, etc.
>
> Can you give me an example of deploying ANAME outside the zone APEX 
> that
> is not solved by allowing a CNAME to point to a CNAME (which most code 
> I
> think already allows anyway)

One PowerDNS user is using ALIAS (our ANAME precursor, if you will) 
because he is by policy not allowed to CNAME into unsigned zones, and 
his app is hosted on Amazon with ELB which means Route53 is mandatory 
for him.

Kind regards,
-- 
Peter van Dijk
PowerDNS.COM BV - https://www.powerdns.com/