Re: [dnsext] SRV and wildcard CNAME

Phillip Hallam-Baker <hallam@gmail.com> Sun, 20 February 2011 01:17 UTC

Return-Path: <dnsext-bounces@ietf.org>
X-Original-To: namedroppers-archive-gleetwall6@lists.ietf.org
Delivered-To: ietfarch-namedroppers-archive-gleetwall6@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A4CD93A7051; Sat, 19 Feb 2011 17:17:42 -0800 (PST)
X-Original-To: dnsext@core3.amsl.com
Delivered-To: dnsext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0736B3A7051 for <dnsext@core3.amsl.com>; Sat, 19 Feb 2011 17:17:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.537
X-Spam-Level:
X-Spam-Status: No, score=-3.537 tagged_above=-999 required=5 tests=[AWL=0.061, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yxuNyG1kfuSZ for <dnsext@core3.amsl.com>; Sat, 19 Feb 2011 17:17:40 -0800 (PST)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id CF0F63A6A6E for <dnsext@ietf.org>; Sat, 19 Feb 2011 17:17:39 -0800 (PST)
Received: by iwl42 with SMTP id 42so1732349iwl.31 for <dnsext@ietf.org>; Sat, 19 Feb 2011 17:18:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=u/WMtHgzec8GmeDW6/Q2VR7LYtBOdF6gp8ibHDQDJDA=; b=jcKaLNbmcEPFrYpGPGlDDzsPJa7rl0HN1n2zxT1Csr2JaYMKm7evj82/9VkVQOU0xj RTcBVMYw8TyY8rL8fXNk3DJ7OhRYrk1LXGmTe161fo7hROmZ5HxIZRmM+2JjqrdrFIqp olXiftOn833E6joaGKpXl7TLrOOA2vZdI+H80=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=sCLFoHYVPYgie9Rw0IVHAetgkdp5sHVaM3E/A0Npb4dcKWShQuAbolaAoVphgFDhb+ BbXW8iCl02Mm+mmS58XSURrR9/MZg3fF0nt240II84CmCsCiU4yvZpotAcLQLrmPygxP QdHtK5LSXNRb9u17BiGPHWt0IWiOOA3L86JNQ=
MIME-Version: 1.0
Received: by 10.42.4.1 with SMTP id 1mr2982186icq.370.1298164697406; Sat, 19 Feb 2011 17:18:17 -0800 (PST)
Received: by 10.42.215.140 with HTTP; Sat, 19 Feb 2011 17:18:17 -0800 (PST)
In-Reply-To: <4D5E08E4.8060106@necom830.hpcl.titech.ac.jp>
References: <20110216032120.43474.qmail@joyce.lan> <alpine.LSU.2.00.1102161143180.5244@hermes-1.csi.cam.ac.uk> <20110216212930.57D64A3F344@drugs.dv.isc.org> <4D5D24F3.70206@gis.net> <20110217231720.1FCF3A49096@drugs.dv.isc.org> <4D5E08E4.8060106@necom830.hpcl.titech.ac.jp>
Date: Sat, 19 Feb 2011 17:18:17 -0800
Message-ID: <AANLkTikjBvndD91q1jQeU9Q45qZyJbBs8t_wZkFezSfa@mail.gmail.com>
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Cc: dnsext@ietf.org
Subject: Re: [dnsext] SRV and wildcard CNAME
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsext>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0761060634=="
Sender: dnsext-bounces@ietf.org
Errors-To: dnsext-bounces@ietf.org

It does indeed. And worse, it works for

_null._random.example.com  SRV...

And other non existent protocols.

There is a way to fix the issue. Instead of resolving in a single step, a
two step resolution is performed. The first step being for an unprefixed
name. This will result in either 'not found' or a canonical name being
returned. The prefix is applied to the canonical name in the second phase.


On Thu, Feb 17, 2011 at 9:51 PM, Masataka Ohta <
mohta@necom830.hpcl.titech.ac.jp> wrote:

> Mark Andrews wrote:
>
> > this include "www.example.net CNAME example.net".
>
> That's a problem. But...
>
> > Additionally people are too lazy to add records for each virtual
> > service in the DNS so they use "* CNAME server" which makes using
> > SRV hard as it requires prepended labels.
>
> Doesn't it mean:
>
>        *.example.com    CNAME srv.example.com
>        srv.example.com  SRV   Priority Weight Port Target
>
> works as:
>
>        _http._tcp.www.example.com SRV  Priority Weight Port Target
>
> ?
>                                                 Masataka Ohta
> _______________________________________________
> dnsext mailing list
> dnsext@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsext
>



-- 
Website: http://hallambaker.com/
_______________________________________________
dnsext mailing list
dnsext@ietf.org
https://www.ietf.org/mailman/listinfo/dnsext