IETF Logo Mail Archive

Re: [DNSOP] fyi [Pdns-users] Please test: ALIAS/ANAME apex record in PowerDNS

Colm MacCárthaigh <colm@allcosts.net> Mon, 22 September 2014 14:41 UTC

Return-Path: <colm@allcosts.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B69C1A1AFB for <dnsop@ietfa.amsl.com>; Mon, 22 Sep 2014 07:41:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.678
X-Spam-Level:
X-Spam-Status: No, score=-1.678 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7] autolearn=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 JlHR571aOYKy for <dnsop@ietfa.amsl.com>; Mon, 22 Sep 2014 07:41:33 -0700 (PDT)
Received: from mail-oa0-f52.google.com (mail-oa0-f52.google.com [209.85.219.52]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 108371A1AF7 for <dnsop@ietf.org>; Mon, 22 Sep 2014 07:41:33 -0700 (PDT)
Received: by mail-oa0-f52.google.com with SMTP id o6so1662841oag.25 for <dnsop@ietf.org>; Mon, 22 Sep 2014 07:41:32 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=Dg6S0+X3tGKa+qj207RKgQNIS/Tgb0rvJUaF9liEWbQ=; b=d9+lz2LKLJ3+cdKl/a6C+yRZ3EjJoOP54+rxjLIk3l+6qEPVe516wOjA77rFbEV0bU NRQ28bFhgHRpoDpRdmdxOd5kKNVVoLsgoS/qXgHKTURCkSRdZqTSdMiisRPWHB8vLKL2 TzeDVwZ1R1ELuSeK/dCR6Njxy2//wtybcg9hkvK3CZywqSP3MpKnr2Rz2uzq4U4RCfv5 yrpe6FuPZXPfBTojAkXe8C4++ZKjBNwNztvY569qTn/Ww5MG6o0E9Q7+dZyMQOUR73Na 5jQ/zvxTgg2mOhbG5pszFU29Dm4mMedVXFkdXjhEOsoWS0cU9EEzraUv1jfhSA0jLSPl 7zeg==
X-Gm-Message-State: ALoCoQmRCOzZv58sl3IEUS+nqMcuCiHvUiBjblVX/BVB2g1I1m2lBVVGGK4jjfG9FGCWjmRQDRsj
MIME-Version: 1.0
X-Received: by 10.182.65.65 with SMTP id v1mr27887799obs.58.1411396892414; Mon, 22 Sep 2014 07:41:32 -0700 (PDT)
Received: by 10.76.110.206 with HTTP; Mon, 22 Sep 2014 07:41:32 -0700 (PDT)
In-Reply-To: <alpine.LSU.2.00.1409221459020.3000@hermes-1.csi.cam.ac.uk>
References: <20140921115222.GB16178@xs.powerdns.com> <541F1AE8.6010709@redbarn.org> <CAAF6GDdttYNDBDSROiHSGkkvRZ5Pxfm0W_d68x=POXgU_SsYOg@mail.gmail.com> <541F569D.9040508@redbarn.org> <20140922132131.GA98041@mx1.yitter.info> <alpine.LSU.2.00.1409221459020.3000@hermes-1.csi.cam.ac.uk>
Date: Mon, 22 Sep 2014 07:41:32 -0700
Message-ID: <CAAF6GDc1=wcLXg1nfiqoXXH7ZmNWhcwsJfhAJnsuhiv8wJPvQA@mail.gmail.com>
From: Colm MacCárthaigh <colm@allcosts.net>
To: Tony Finch <dot@dotat.at>
Content-Type: text/plain; charset="UTF-8"
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/UqzlRWuE9hzOyLBKns1jGjKc7Wc
Cc: "dnsop@ietf.org" <dnsop@ietf.org>, Andrew Sullivan <ajs@anvilwalrusden.com>
Subject: Re: [DNSOP] fyi [Pdns-users] Please test: ALIAS/ANAME apex record in PowerDNS
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 22 Sep 2014 14:41:34 -0000

On Mon, Sep 22, 2014 at 7:06 AM, Tony Finch <dot@dotat.at> wrote:
> The fun bit is that an auth server implementing some kind of proxying
> ANAME is in a position very like Google and OpenDNS. That is, if the
> target of the ANAME is a hostname provided by Akamai or CloudFlare or
> whoever, and if the auth server is going to proxy the answer faithfully,
> then it has to implement client-subnet.

I wonder if the best thing to do would be to define an ANAME/AAAANAME
that can be negotiated by resolvers. If the resolver supports it (it
can let the auth know via EDNS0) then the ANAME/AAAANAME is returned
without resolution. If the resolver doesn't support it, then a
synthetic A/AAAA can be returned.

-- 
Colm

v2.23.0 | Report a Bug | By Email