From owner-freebsd-questions@FreeBSD.ORG Mon Jun 6 01:25:11 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 50A1F16A41C for ; Mon, 6 Jun 2005 01:25:11 +0000 (GMT) (envelope-from rmarella@gmail.com) Received: from ms-smtp-01-eri0.socal.rr.com (ms-smtp-01-qfe0.socal.rr.com [66.75.162.133]) by mx1.FreeBSD.org (Postfix) with ESMTP id 21DB343D53 for ; Mon, 6 Jun 2005 01:25:11 +0000 (GMT) (envelope-from rmarella@gmail.com) Received: from [10.0.0.101] (cpe-66-8-186-59.hawaii.res.rr.com [66.8.186.59]) by ms-smtp-01-eri0.socal.rr.com (8.12.10/8.12.7) with ESMTP id j561P8Ff009956; Sun, 5 Jun 2005 18:25:08 -0700 (PDT) Message-ID: <42A3A5F4.8090807@gmail.com> Date: Sun, 05 Jun 2005 15:25:08 -1000 From: Robert Marella User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050512 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Robert Huff References: <5EEBE9C3C61D1142994C6B620C51E847110B80@depot.weblinkmo.com> <17059.37867.174248.688500@jerusalem.litteratus.org> In-Reply-To: <17059.37867.174248.688500@jerusalem.litteratus.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Symantec AntiVirus Scan Engine Cc: freebsd-questions@freebsd.org Subject: Re: ssh delays 40 seconds X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Jun 2005 01:25:11 -0000 Robert Huff wrote: > Richard J. Valenta writes: > > >> I had this problem in the past, and it was due to DNS problems where my >> IP from the client machine was unable to be resolved... but I think it >> took longer than 40 seconds. I mentioned this in this list before, a >> search of the list may help. > > > Affirmed for the general case. "30 second delay, then normal > network activity" _screams_ DNS misconfiguration, usually but not > always in the client side. > > > Robert Huff Forgive me if I am dense. According to the readout of "ssh -vvv gateway" the connection is made immediately. Does that not indicate that it knew where to go? The contents of "/etc/resolv.conf" on all of my systems is the same: [frankie] ~> cat /etc/resolv.conf search hawaii.rr.com nameserver 24.25.227.33 nameserver 24.25.227.66 nameserver 24.25.227.64 I even commented out the other 2 and tried each nameserver one at a time and it was able to resolve www.freebsd.org Am I looking in the wrong place? Again, if I am ignorant, please excuse me. Perhaps, point me to a document. Thanks to all who responded Robert