Re: [dnsext] Naked domain resolution with DNSSEC

"Jiankang Yao" <yaojk@cnnic.cn> Fri, 25 October 2013 09:26 UTC

Return-Path: <yaojk@cnnic.cn>
X-Original-To: dnsext@ietfa.amsl.com
Delivered-To: dnsext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BC2D11E834F for <dnsext@ietfa.amsl.com>; Fri, 25 Oct 2013 02:26:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.356
X-Spam-Level:
X-Spam-Status: No, score=-99.356 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3A1RU4UOYuS8 for <dnsext@ietfa.amsl.com>; Fri, 25 Oct 2013 02:25:58 -0700 (PDT)
Received: from cnnic.cn (smtp.cnnic.cn [218.241.118.7]) by ietfa.amsl.com (Postfix) with SMTP id 6B39B11E839F for <dnsext@ietf.org>; Fri, 25 Oct 2013 02:25:52 -0700 (PDT)
X-EYOUMAIL-SMTPAUTH: yaojk@cnnic.cn
Received: from unknown127.0.0.1 (HELO healthyao-think) (127.0.0.1) by 127.0.0.1 with SMTP; Fri, 25 Oct 2013 17:25:46 +0800
Date: Fri, 25 Oct 2013 17:25:48 +0800
From: Jiankang Yao <yaojk@cnnic.cn>
To: Dave Lawrence <tale@dd.org>, Kumar Ashutosh <askuma@microsoft.com>
References: <E66B38BB793BAF439EF374F3E7EBEE4647EAD8D5@SINEX14MBXC405.southpacific.corp.microsoft.com> <21069.41000.63116.736893@gro.dd.org> <F04702D34F7A2740A330302703120864384C8916@SINEX14MBXC421.southpacific.corp.microsoft.com> <21074.61535.976353.482373@gro.dd.org> <E66B38BB793BAF439EF374F3E7EBEE464B6202F6@SINEX14MBXC415.southpacific.corp.microsoft.com> <21095.58207.781300.353688@gro.dd.org> <E66B38BB793BAF439EF374F3E7EBEE464B620758@SINEX14MBXC415.southpacific.corp.microsoft.com> <C94CB03B-44C8-4792-9097-141D812EC01C@rfc1035.com> <E66B38BB793BAF439EF374F3E7EBEE464B620972@SINEX14MBXC415.southpacific.corp.microsoft.com>, <21096.7524.908259.719737@gro.dd.org>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.0.1.92[cn]
Mime-Version: 1.0
Message-ID: <2013102517253369957870@cnnic.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart705473253804_=----"
Cc: Thirunadha Reddy <thirunr@microsoft.com>, "dnsext@ietf.org Group" <dnsext@ietf.org>, Sourav Sain <sosain@microsoft.com>
Subject: Re: [dnsext] Naked domain resolution with DNSSEC
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: yaojk <yaojk@cnnic.cn>
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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>
X-List-Received-Date: Fri, 25 Oct 2013 09:26:02 -0000


From: Dave Lawrence
Date: 2013-10-24 03:03
To: Kumar Ashutosh
CC: Sourav Sain; dnsext@ietf.org Group; Thirunadha Reddy
Subject: Re: [dnsext] Naked domain resolution with DNSSEC
Kumar Ashutosh writes:
> I agree on CNAME behaviour. My concern here is what option does the
> customer have in case he needs contoso.com and www.contoso.com both to
> be redirected to say contoso.dnsprovider.com 

BNAME, which directs both itself and its children, may solve it. the draft about BNAME was discussed 3 years ago.