From owner-freebsd-current@FreeBSD.ORG Fri Feb 17 16:01:41 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 0708616A435; Fri, 17 Feb 2006 16:01:41 +0000 (GMT) (envelope-from foo@virtual-voodoo.com) Received: from mailhub247.itcs.purdue.edu (mailhub247.itcs.purdue.edu [128.210.5.247]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8EF5143D48; Fri, 17 Feb 2006 16:01:40 +0000 (GMT) (envelope-from foo@virtual-voodoo.com) Received: from [192.168.1.47] (pool-71-98-109-59.ipslin.dsl-w.verizon.net [71.98.109.59]) (authenticated bits=0) by mailhub247.itcs.purdue.edu (8.13.4/8.13.4/external-auth-smtp) with ESMTP id k1HG1cAp021780 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 17 Feb 2006 11:01:39 -0500 Message-ID: <43F5F531.2070900@virtual-voodoo.com> Date: Fri, 17 Feb 2006 11:09:21 -0500 From: Foo 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> In-Reply-To: <20060216094646.8qqpg683cwk0o0ww@netchild.homeip.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-PMX-Version: 4.7.1.128075 X-PerlMx-Virus-Scanned: Yes X-Mailman-Approved-At: Fri, 17 Feb 2006 16:25:02 +0000 Cc: re@freebsd.org, current@freebsd.org Subject: Re: reversed behavior with nsswitch.conf X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: foo@virtual-voodoo.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Feb 2006 16:01:41 -0000 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. Hope this helps. Joel Alexander Leidinger wrote: >Hi, > >yesterday I debugged a mail problem where the reverse DNS of the receiver is >somewhat fucked up (for one receiver the DNS resolving chain was: HostA -> >IP-A -> HostB -> IP-B -> HostB, for the other receiver there was no reverse >DNS). > >Sendmail doen't like this, but there are ways to circumvent this. So I added >the hosts in question to /etc/hosts (nsswitch contains "hosts: files dns"), >and thought this will solve it. It didn't. > >A temporary (as in "to get those 10 mails out") work-around of "hosts: files" >proved that the solution of adding the hosts to /etc/hosts works as expected. > >The current solution for the general case is to use "hosts: dns files". It >gets the correct values for the buggy remote hosts from /etc/hosts, and >averything else from DNS. > >So it seems the order of the use of the entries in nsswitch.conf is reversed. > >I noticed this on a 6.0 system. I can't test this on a -current system right >now (maybe tomorrow or at the weekend), and I don't have a RELENG_6 system. > >So if someone can confirm if this bug is visible on -current and on RELENG_6: > - a fix can be MFCed if it is fixed in -current > - someone could try to fix it if the same problem exists in -current > - an errata can be added to the release notes of 6.1 if it isn't > fixed until the release (that's the reason why I CCed re@) > >Bye, >Alexander. > > >