From owner-freebsd-stable@FreeBSD.ORG Wed Mar 26 11:00:22 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 E121937B404 for ; Wed, 26 Mar 2003 11:00:22 -0800 (PST) Received: from tamu-relay.tamu.edu (smtp-relay.tamu.edu [165.91.143.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 189F243F85 for ; Wed, 26 Mar 2003 11:00:22 -0800 (PST) (envelope-from daved@nostrum.com) Received: from nostrum.com (vpn-0002.tamulink.tamu.edu [165.91.47.2]) by tamu-relay.tamu.edu (8.12.8/8.12.8) with ESMTP id h2QJ0Eut015361; Wed, 26 Mar 2003 13:00:15 -0600 (CST) Date: Wed, 26 Mar 2003 13:00:17 -0600 Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v551) To: Terry Lambert From: David J Duchscher In-Reply-To: <3E816354.E5FDA886@mindspring.com> Message-Id: <2F60240B-5FBD-11D7-8B57-0003930B3DA4@nostrum.com> Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.551) X-Spam-Status: No, hits=-21.6 required=5.0 tests=EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT, REPLY_WITH_QUOTES,USER_AGENT_APPLEMAIL autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) cc: stable@FreeBSD.ORG Subject: Re: Resolver Issues (non valid hostname characters) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list 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:00:25 -0000 On Wednesday, March 26, 2003, at 02:22 AM, Terry Lambert wrote: > David J Duchscher wrote: >> On Tuesday, March 25, 2003, at 09:32 PM, Terry Lambert wrote: >>> 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. > > I would like to see a program, with source code, that can > determine, with 100% accuracy, whether or not "_" is allowed, > and prints out either: > > This system supports _, in violation of RFC-952. > > Or: > > This system complies with RFC-952. > > Then I would like to see the output of this program run on the > systems, other than Linux, which you claim violate RFC-952. You > can include Linux, if you want, to, for comparison purposes. Since I don't believe I can create such a program to your specification, I guess you win. All I can say is that gethostbyname will return host names with underscore character on the those operating systems. >>>>> What is the first maxim of protocol design? >>>>> >>>>> "Be generous in what you accept, strict in what you generate". >>> >>> 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. > > Sounds like you picked the wrong interfaces to want to have fixed. Yep. DaveD