From owner-freebsd-arch@FreeBSD.ORG Sun Mar 30 09:46:28 2003 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5C51037B401 for ; Sun, 30 Mar 2003 09:46:28 -0800 (PST) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8BB6243F93 for ; Sun, 30 Mar 2003 09:46:27 -0800 (PST) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.8/8.12.3) with ESMTP id h2UHkQA7020780; Sun, 30 Mar 2003 10:46:26 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sun, 30 Mar 2003 10:45:01 -0700 (MST) Message-Id: <20030330.104501.49852624.imp@bsdimp.com> To: des@ofug.org From: "M. Warner Losh" In-Reply-To: References: <20030330.060534.18864762.imp@bsdimp.com> X-Mailer: Mew version 2.1 on Emacs 21.2 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable cc: arch@freebsd.org Subject: Re: Allow underscores in DNS names X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Mar 2003 17:46:29 -0000 In message: des@ofug.org (Dag-Erling Sm=F8rgrav) writes: : "M. Warner Losh" writes: : > True. However, they are still relevant today. '_' is illegal in D= NS : > names : = : Says the RFC. IIRC, BIND traditionally did not enforce this, though : it does now for A records in master zones unless you change the : "check-names" setting (it seems to allow it for TXT records though). Bind has enforced this for a long time. : > is rejected by the majority of hosts on the internet : = : Wrong. We (*BSD) are pretty much the only ones not to accept : underscores in host names. I've tested Windows XP, Solaris 8 and : Linux 2.4.18; feel free to try 'ping under_score.ofug.org' on other : systems and report your findings here. This must be new because bind has enforced this for a long time. : > and : > generally is a bad idea. : = : I don't see why, and I've never heard any other argument against it : than "the RFC says so". It makes it harder for the script kiddies to write eggs for buffer overflow exploits in the DNS system. That's the whole reason that the bind folks started adding the restrictive character set. Also, if you produce characters outside the character set, then you are generating illegal packets, and there is (used to be) a lot of software that would choke in subtle ways. Warner