From owner-freebsd-stable@FreeBSD.ORG Wed Mar 26 11:42:46 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C33E137B40A for ; Wed, 26 Mar 2003 11:42:46 -0800 (PST) Received: from bilver.wjv.com (user38.net339.fl.sprint-hsd.net [65.40.24.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id AEF8043FA3 for ; Wed, 26 Mar 2003 11:42:43 -0800 (PST) (envelope-from bv@wjv.com) Received: from bilver.wjv.com (localhost.wjv.com [127.0.0.1]) by bilver.wjv.com (8.12.6/8.12.6) with ESMTP id h2QJgd6u048709 for ; Wed, 26 Mar 2003 14:42:39 -0500 (EST) (envelope-from bv@wjv.com) Received: (from bv@localhost) by bilver.wjv.com (8.12.6/8.12.6/Submit) id h2QJgcG7048708 for freebsd-stable@freebsd.org; Wed, 26 Mar 2003 14:42:38 -0500 (EST) Date: Wed, 26 Mar 2003 14:42:37 -0500 From: Bill Vermillion To: freebsd-stable@freebsd.org Message-ID: <20030326194237.GD44655@wjv.com> References: <20030326070146.AF79D37B405@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030326070146.AF79D37B405@hub.freebsd.org> Organization: W.J.Vermillion / Orlando - Winter Park ReplyTo: bv@wjv.com User-Agent: Mutt/1.5.1i X-Spam-Status: No, hits=-26.6 required=5.0 tests=IN_REP_TO,QUOTED_EMAIL_TEXT,QUOTE_TWICE_1,REFERENCES, REPLY_WITH_QUOTES,USER_AGENT_MUTT autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) Subject: Re: non valid host names X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: bv@wjv.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Mar 2003 19:42:49 -0000 > On Tuesday, March 25, 2003, at 09:32 PM, Terry Lambert wrote: > > David J Duchscher wrote: > >>> If this is committed before RFC-952 is updated, FreeBSD users > >>> can now define host names that break other machines on the net > >>> which are strictly conformant to RFC-952. > >> > >> Which will just make us behave like rest of the world. I have tested > >> resolvers on Solaris, Windows, MacOS X, MacOS 9, IRIX, Linux, AIX. > >> They all will resolve a name with an underscore character. Only the > >> *BSD boxes fail because of the check. > > > > Actually, anyone who took the original ISC code, or the FreeBSD code, > > will end up having problems. Including AIX, Solaris, MacOS X. > Unless they have modified the code which all the above OSes seem to > have done since they do not show the behavior. > >>> What is the first maxim of protocol design? > >>> > >>> "Be generous in what you accept, strict in what you generate". > >> > >> Which is why I would argue that the patch should be committed, maybe > >> with an option to enable it. We are talking about the resolver, not a > >> DNS or hostname server. The resolver should resolve the name, be > >> generous. It just depends at what level you apply the maxim. The > >> check should be in the DNS server not in the resolver IMHO. > > > > You apply the maxim to each interface, seperately. For example, > > FreeBSD should not allow the configuration of host names with > > "_" in them, but it should, perhaps, permit them to be looked up. > I can agree with this statement. Unfortunately, FreeBSD doesn't > do this in many ways. Example, you can set a hostname with a > underscore in it. You can even use an underscore in the name in > the host file and everything will work. You just can't look up > the name via DNS. One of the first times I brought up a DNS server was about 1994 for a local community college. 'twas a mixed bag and the only Unix system was their internet gateway - with everyting else being Novell except the mail handlers locally being OS/2. At that time they had machines with underscores - I believe they were the OS/2 machines. I told them they should make plans to change them as the underscore was being eliminated. They did nothing until three years later - '97 or '98 - when they started having problems. There has been plenty of warnings so I have no sympathy for those who had 8 years to plan for this. Bill -- Bill Vermillion - bv @ wjv . com