From owner-freebsd-stable Mon Mar 24 20:18:40 2003 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 DD75B37B401 for ; Mon, 24 Mar 2003 20:18:36 -0800 (PST) Received: from fe3.cox-internet.com (fe3-cox.cox-internet.com [66.76.2.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 479BA43F3F for ; Mon, 24 Mar 2003 20:18:36 -0800 (PST) (envelope-from daved@nostrum.com) Received: from nostrum.com ([208.180.29.144]) by fe3.cox-internet.com (InterMail vK.4.04.00.02 201-232-139-20020803 license 9a2f9096933fa391a6c2fc942f8b01bd) with ESMTP id <20030325041835.RKDF20598.fe3@nostrum.com> for ; Mon, 24 Mar 2003 22:18:35 -0600 Date: Mon, 24 Mar 2003 22:18:37 -0600 Mime-Version: 1.0 (Apple Message framework v551) Content-Type: text/plain; charset=US-ASCII; format=flowed Subject: Resolver Issues (non valid hostname characters) From: David J Duchscher To: freebsd-stable@freebsd.org Content-Transfer-Encoding: 7bit Message-Id: X-Mailer: Apple Mail (2.551) X-Spam-Status: No, hits=-2.1 required=5.0 tests=USER_AGENT_APPLEMAIL autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It seems that the use of invalid characters in hostnames is cropping up more and more. Besides complaining to the offending site which often doesn't work, I was wondering if these restrictions on FreeBSD should be re-examined. At this time, it seems that many OSes are no longer enforcing this requirement or never have. In my case, I am running into a hostnames with an underscore character in the name. It seems that Linux, MacOS X, Solaris and Windows all allow this hostname to resolve but FreeBSD, as well as the other *BSD, reject it. Should FreeBSD follow suit? DaveD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message