From owner-freebsd-bugs@FreeBSD.ORG  Mon Aug 30 13:28:53 2004
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 71FB516A4CE; Mon, 30 Aug 2004 13:28:53 +0000 (GMT)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 4F5AC43D68; Mon, 30 Aug 2004 13:28:53 +0000 (GMT)
	(envelope-from yar@FreeBSD.org)
Received: from freefall.freebsd.org (yar@localhost [127.0.0.1])
	i7UDSrcn054949;	Mon, 30 Aug 2004 13:28:53 GMT
	(envelope-from yar@freefall.freebsd.org)
Received: (from yar@localhost)
	by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i7UDSrSf054945;
	Mon, 30 Aug 2004 13:28:53 GMT
	(envelope-from yar)
Date: Mon, 30 Aug 2004 13:28:53 GMT
From: Yar Tikhiy <yar@FreeBSD.org>
Message-Id: <200408301328.i7UDSrSf054945@freefall.freebsd.org>
To: rosti_bsd@yahoo.com, yar@FreeBSD.org, freebsd-bugs@FreeBSD.org
Subject: Re: bin/62139: User cannot login through telnet or ssh because of
	reverse resolving delay
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Aug 2004 13:28:53 -0000

Synopsis: User cannot login through telnet or ssh because of reverse resolving delay

State-Changed-From-To: open->feedback
State-Changed-By: yar
State-Changed-When: Mon Aug 30 13:19:01 GMT 2004
State-Changed-Why: 
To my mind, this is a host configuration issue.  First, you
may list multiple nameservers in your resolv.conf so that
should one of them fail, the others will still respond to
queries.  Second, the resolver timeout and attempts may be
set to a lower value (see resolver(5) for details) if your
network can suffer from all its nameservers being unavailable.
Please also note that some ways of ssh authentication may
rely on a name service being available.

http://www.freebsd.org/cgi/query-pr.cgi?pr=62139