From owner-freebsd-questions@FreeBSD.ORG Mon Mar 21 14:36:14 2005 Return-Path: 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 04B8A16A4CE for ; Mon, 21 Mar 2005 14:36:14 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 35E3943D1F for ; Mon, 21 Mar 2005 14:36:13 +0000 (GMT) (envelope-from gary.smithe@gmail.com) Received: by wproxy.gmail.com with SMTP id 70so1244410wra for ; Mon, 21 Mar 2005 06:36:12 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=dizO9sJA07zdPzCIvxANme7nghsmDv2OBWWfvR0jaAjS9pH4mI6CQttNnGek0fqdrnHSoT8bk1j4zffvmhkXTBBrQM96XRHwGZuHlXQNaKz0fC3Lv+f0AankFoeBhI3aSo+5qQ1X37Y0V+e31PD/mbzTjtyYs/iQ+ZOfXiuFk+8= Received: by 10.54.30.77 with SMTP id d77mr416945wrd; Mon, 21 Mar 2005 06:36:05 -0800 (PST) Received: by 10.54.41.29 with HTTP; Mon, 21 Mar 2005 06:35:41 -0800 (PST) Message-ID: Date: Mon, 21 Mar 2005 08:35:41 -0600 From: Gary Smithe To: freebsd-questions@freebsd.org In-Reply-To: <423E116D.50805@usmstudent.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: <423E116D.50805@usmstudent.com> Subject: Re: ssh password delay X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Gary Smithe List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Mar 2005 14:36:14 -0000 > I have done quite a bit of googling and I realize that the problem > likely has something to do with reverse DNS lookups. But, I don't know > how to pinpoint the problem from there. I've basically been playing > with the /etc/resolv.conf and /etc/hosts settings. In my hosts file, I > have an entry for the private IP of my Linux box with its hostname > (which is not a FQDN) and my resolv.conf file looks like: > > domain myrealdomain.com //I just added this, but no noticeable help > search myrealdomain.com > nameserver my.ip's.dns.numbers > nameserver my.ip's.dns.numbers2 > [SNIP] > TIA, > backdoc > If that is your resolv.conf, then that explains some things. Your box is looking at the ISP for name resolution and the ISP has no idea (nor could care) what your internal LAN address space is. Change the resolv.conf to look at itself (127.0.0.1) and setup BIND with some simple DNS and RDNS records. You could use pretty much any box on your network for DNS, but the key is that it has to know about the internal space. GS