From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 5 09:04:11 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B3C1316A4BF for ; Fri, 5 Sep 2003 09:04:11 -0700 (PDT) Received: from oniws.ca (oniws.ca [67.69.49.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD19643FB1 for ; Fri, 5 Sep 2003 09:04:10 -0700 (PDT) (envelope-from Dwayne.MacKinnon@xwave.com) Received: from xwave.com ([192.168.0.126]) by oniws.ca (8.12.8p1/8.12.8) with ESMTP id h85G490w000323; Fri, 5 Sep 2003 12:04:09 -0400 (EDT) (envelope-from Dwayne.MacKinnon@xwave.com) Message-ID: <3F58B3F4.3020502@xwave.com> Date: Fri, 05 Sep 2003 12:04:04 -0400 From: Dwayne MacKinnon Organization: xwave User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20030702 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kris Kennaway References: <3F589E94.1080508@xwave.com> <20030905154646.GA59881@rot13.obsecurity.org> In-Reply-To: <20030905154646.GA59881@rot13.obsecurity.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-hackers@freebsd.org Subject: Re: PUzzling sshd behaviour X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Dwayne.MacKinnon@xwave.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Sep 2003 16:04:11 -0000 Kris Kennaway wrote: > On Fri, Sep 05, 2003 at 10:32:52AM -0400, Dwayne MacKinnon wrote: > > >>Anyone else see this type of thing before? I did some research on the >>lists but all I ever saw was a problem with reading resolv.conf. That's >>not the case here, because it's definitely picking up the nameserver >>from that file. > > > The fact that sshd requires reverse IP resolution is well-known > behaviour. It's probably the most common FAQ about sshd ("Why is my > login taking 60 seconds to present the password prompt?"). > > Kris That much I know. I was just wondering why the daemon is trying DNS lookup when the IP in question is listed in /etc/hosts. I thought listings in /etc/hosts would supercede the need for a DNS lookup. Of course, I could be wrong... it wouldn't be the first time. :-) Cheers, DMK