Re: [DNSOP] Unusual behavior (wildcarding) on .cn TLD
Stephane Bortzmeyer <bortzmeyer@nic.fr> Mon, 02 November 2009 13:10 UTC
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dnsop@core3.amsl.com
Delivered-To: dnsop@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5D9F53A68F7 for <dnsop@core3.amsl.com>; Mon, 2 Nov 2009 05:10:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.438
X-Spam-Level:
X-Spam-Status: No, score=-4.438 tagged_above=-999 required=5 tests=[AWL=-0.603, BAYES_40=-0.185, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4]
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 Mvp+mxEQSWTy for <dnsop@core3.amsl.com>; Mon, 2 Nov 2009 05:10:57 -0800 (PST)
Received: from mx2.nic.fr (mx2.nic.fr [192.134.4.11]) by core3.amsl.com (Postfix) with ESMTP id 3A4FB3A6894 for <dnsop@ietf.org>; Mon, 2 Nov 2009 05:10:57 -0800 (PST)
Received: from mx2.nic.fr (localhost [127.0.0.1]) by mx2.nic.fr (Postfix) with SMTP id 30F8C1C016B; Mon, 2 Nov 2009 14:06:15 +0100 (CET)
Received: from relay1.nic.fr (relay1.nic.fr [192.134.4.162]) by mx2.nic.fr (Postfix) with ESMTP id 2CE641C0156; Mon, 2 Nov 2009 14:06:15 +0100 (CET)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [192.134.4.69]) by relay1.nic.fr (Postfix) with ESMTP id 20E32A1D94C; Mon, 2 Nov 2009 14:06:15 +0100 (CET)
Date: Mon, 02 Nov 2009 14:06:15 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
Message-ID: <20091102130615.GA25222@nic.fr>
References: <DDC29F8F-CD6F-4A1C-826D-FB5FE6733CCA@ICSI.Berkeley.EDU>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <DDC29F8F-CD6F-4A1C-826D-FB5FE6733CCA@ICSI.Berkeley.EDU>
X-Operating-System: Debian GNU/Linux 5.0.3
X-Kernel: Linux 2.6.26-2-686 i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] Unusual behavior (wildcarding) on .cn TLD
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 02 Nov 2009 13:10:58 -0000
On Fri, Oct 30, 2009 at 11:54:06AM -0700, Nicholas Weaver <nweaver@ICSI.Berkeley.EDU> wrote a message of 49 lines which said: > Has anyone else observed the following behavior for the .cn TLD, Yes. It was reported by Florian Weimer on the dns-operations mailing list. > one authoritative server (NS.CERNET.NET) wildcards invalid domains, > but the others (a-e.dns.cn) do not? It's more fun than that: it also depends if the QNAME is 7-bits ASCII or not. > Anyone know someone operationally involved with the .cn TLD to know > if this is deliberate and, if so, why? I reported the issue to CNNIC. I'll be in Beijing tomorrow so we may discuss it in more detail.
- [DNSOP] Unusual behavior (wildcarding) on .cn TLD Nicholas Weaver
- Re: [DNSOP] Unusual behavior (wildcarding) on .cn… Stephane Bortzmeyer