From owner-freebsd-questions Thu Mar 18 9:22:59 1999 Delivered-To: freebsd-questions@freebsd.org Received: from java.dpcsys.com (java.dpcsys.com [206.16.184.7]) by hub.freebsd.org (Postfix) with ESMTP id 044AF14E45 for ; Thu, 18 Mar 1999 09:22:48 -0800 (PST) (envelope-from dan@dpcsys.com) Received: from localhost (dan@localhost) by java.dpcsys.com (8.9.1a/8.9.1) with SMTP id JAA22153; Thu, 18 Mar 1999 09:23:06 -0800 (PST) Date: Thu, 18 Mar 1999 09:23:06 -0800 (PST) From: Dan Busarow To: Brett Glass Cc: questions@FreeBSD.ORG Subject: Re: Oddity in name resolution In-Reply-To: <4.1.19990317220420.03f15d50@localhost> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 17 Mar 1999, Brett Glass wrote: > A FreeBSD system here in the lab is having trouble resolving host names > with underscores in them. Yes, I know, they're really not SUPPOSED to have > underscores in them, but many do. For example, the mail exchanger for The > Computer Museum in Boston is museum_alpha.tcm.org. They have no secondary > MX, so mail sent to anyone there just bounces. We may also be missing > INCOMING mail from them, since the mailer may reject mail from any host > whose name it can't resolve. With bind8 you can control this, someone may have tightened it up as the default allows these names through. See named.conf options { check-names } The defaults are check-names master fail; check-names slave warn; check-names response ignore; which will not allow *you* to have bad names in a zone you are primary for, will complain about bad names in a domain you are secondary for and allow bad names when querying other zones. Dan -- Dan Busarow 949 443 4172 Dana Point Communications, Inc. dan@dpcsys.com Dana Point, California 83 09 EF 59 E0 11 89 B4 8D 09 DB FD E1 DD 0C 82 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message