From owner-freebsd-stable@FreeBSD.ORG  Sun Dec 19 18:33:05 2004
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 3E61B16A4CE
	for <freebsd-stable@freebsd.org>;
	Sun, 19 Dec 2004 18:33:05 +0000 (GMT)
Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11])
	by mx1.FreeBSD.org (Postfix) with SMTP id 1B32443D1D
	for <freebsd-stable@freebsd.org>;
	Sun, 19 Dec 2004 18:33:04 +0000 (GMT)
	(envelope-from dwmalone@maths.tcd.ie)
Received: from lanczos.maths.tcd.ie by salmon.maths.tcd.ie with SMTP
          id <aa97893@salmon>; 19 Dec 2004 18:33:03 +0000 (GMT)
Date: Sun, 19 Dec 2004 18:33:02 +0000
From: David Malone <dwmalone@maths.tcd.ie>
To: Kov?cs P?ter <kovacspeter2@freemail.hu>
Message-ID: <20041219183302.GA23577@lanczos.maths.tcd.ie>
References: <freemail.20041119190600.63226@fm16.freemail.hu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <freemail.20041119190600.63226@fm16.freemail.hu>
User-Agent: Mutt/1.5.6i
Sender: dwmalone@maths.tcd.ie
cc: freebsd-stable@freebsd.org
Subject: Re: sshd DNS
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Production branch of FreeBSD source code
	<freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 19 Dec 2004 18:33:05 -0000

On Sun, Dec 19, 2004 at 07:06:00PM +0100, Kov?cs P?ter wrote:
> For what sshd needs DNS? If the DNS is unavailable I can't
> log into my computer. How can I resolve this problem, so I
> can still login if the DNS is not available?

I think this is a bad interaction between the default sshd timeouts
and the DNS timeouts. If your reverse DNS is non-responding (as
opposed to just non-existant) then sshd's login timeout can expire
before the DNS lookup finishes making logins impossible. One way
around is to up the login timeout for sshd.

	David.