From owner-freebsd-arch@FreeBSD.ORG Mon Mar 31 13:35:51 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 6620637B401 for ; Mon, 31 Mar 2003 13:35:51 -0800 (PST) Received: from cultdeadsheep.org (charon.cultdeadsheep.org [80.65.226.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3201F43F75 for ; Mon, 31 Mar 2003 13:35:49 -0800 (PST) (envelope-from sheepkiller@cultdeadsheep.org) Received: (qmail 64301 invoked from network); 31 Mar 2003 21:35:47 -0000 Received: from unknown (HELO lucifer.cultdeadsheep.org) (192.168.0.2) by goofy.cultdeadsheep.org with SMTP; 31 Mar 2003 21:35:47 -0000 Date: Mon, 31 Mar 2003 23:35:52 +0200 From: Clement Laforet To: Terry Lambert Message-Id: <20030331233552.16859546.sheepkiller@cultdeadsheep.org> In-Reply-To: <3E864AD1.6C1C3656@mindspring.com> References: <3E864AD1.6C1C3656@mindspring.com> Organization: tH3 cUlt 0f tH3 d3@d sH33p X-Mailer: Sylpheed version 0.8.10 (GTK+ 1.2.10; i386-portbld-freebsd4.6) X-Face: ._cVVRDn#-2((lnfi^P7CoD4htI$4+#G/G)!w|,}H5yK~%(3-C.JlEYbOjJGFwJkt*7N^%z jYeu[;}]}F"3}l5R'l"X0HbvT^D\Q&%deCo)MayY`);TO Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: arch@freebsd.org cc: des@ofug.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: Mon, 31 Mar 2003 21:35:55 -0000 Hi guys, Currently underscore naming is commonly used in LAN/WAN environment. As far as I known, there is only a few (none ?) internet wide host names with underscore. Allowing underscore is useful, but NOT mandatory, but for sysadmins it would be like ssh SUID or ppp SUID : an option when you "build world". I think that "non-vital" options should be supported but they MUST be switched by sysops at build world stage. > > There was a better patch that made it an option in resolv.conf, > rather than turning it on all the time. maybe a variable in make.conf would be better. Ex: make.conf: NOT_REALLY_RFC_COMPLIANT=YES In realworld: #ifndef NOT_REALLY_RFC_COMPLIANT #define hyphenchar(c) ((c) == 0x2d) #else #define hyphenchar(c) ((c) == 0x2d || (c) == 0x5f) #endif To conclude, if BIND authors say "support underscore is a reality we can't eclipse", let's follow them... regards, clem PS : sorry for my poor english ;-)