From owner-freebsd-current@FreeBSD.ORG Sun Feb 19 01:05:59 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E89E216A422; Sun, 19 Feb 2006 01:05:59 +0000 (GMT) (envelope-from jdgunder@purdue.edu) Received: from mailhub246.itcs.purdue.edu (mailhub246.itcs.purdue.edu [128.210.5.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D69443D48; Sun, 19 Feb 2006 01:05:59 +0000 (GMT) (envelope-from jdgunder@purdue.edu) Received: from [192.168.1.108] (d60-65-198-220.col.wideopenwest.com [65.60.220.198]) (authenticated bits=0) by mailhub246.itcs.purdue.edu (8.13.4/8.13.4/external-auth-smtp) with ESMTP id k1J15prE000978 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 18 Feb 2006 20:05:57 -0500 Message-ID: <43F7C46D.2070201@purdue.edu> Date: Sat, 18 Feb 2006 20:05:49 -0500 From: Joel Gunderson User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Alexander Leidinger References: <20060216094646.8qqpg683cwk0o0ww@netchild.homeip.net> <43F5F531.2070900@virtual-voodoo.com> <20060218124212.363545a1@Magellan.Leidinger.net> In-Reply-To: <20060218124212.363545a1@Magellan.Leidinger.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-PMX-Version: 4.7.1.128075 X-PerlMx-Virus-Scanned: Yes Cc: re@freebsd.org, current@freebsd.org, foo@virtual-voodoo.com Subject: Re: reversed behavior with nsswitch.conf X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Feb 2006 01:06:00 -0000 Alexander Leidinger wrote: >Am Fri, 17 Feb 2006 11:09:21 -0500 >schrieb Foo : > > > >>Hi, >> >>I have run into this as well. I am a student in a class that required >>us to set up sendmail in an environment where we don't have access to >>the local DNS, so all our resolution is done via /etc/hosts. I had to >>be able to send email between our three *nix boxes, and it kept breaking >>on the DNS resolution. Initially, I used mailertable entries to >>circumvent the issue since every other strategy I found to turn off DNS >>resolution for sendmail didn't work. However, upon reading this, I >>switched the order of the >>"hosts" settings in nsswitch.conf and got rid of the mailertable entries >>and it worked. So yes, I have run into the issue as well. I am using >>6.0-RELEASE. >> >> > >Is it possible for you to update to 6.1-BETA2? Either by doing a binary >update or by updating /usr/src and doing a build/install? > >I haven't tested it, but someone suggested in private mail to use >"hosts: files [success=return] dns" (he told me this is the way linux >distributions are doing this) which suggests that the documented >default criteria in nsswitch.conf(5) doesn't work. Can you test if this >work-around works? > >Bye, >Alexander. > > > I tried the "hosts: files [success=return] dns" in nsswitch, but it didn't work. I'll have to get back to you on the upgrade thing...if for some reason the machine flips out on the update I don't have time to fix it before checkoffs. Plus my group members would kill me. -Joel