From owner-freebsd-questions@FreeBSD.ORG  Tue Jul  6 17:12:48 2004
Return-Path: <owner-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 0899E16A4D0
	for <freebsd-questions@freebsd.org>;
	Tue,  6 Jul 2004 17:12:48 +0000 (GMT)
Received: from smtp06.web.de (smtp06.web.de [217.72.192.224])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 993C743D3F
	for <freebsd-questions@freebsd.org>;
	Tue,  6 Jul 2004 17:12:47 +0000 (GMT)	(envelope-from nakal@web.de)
Received: from [217.225.229.208] (helo=[217.225.229.208])
	by smtp06.web.de with esmtp (TLSv1:DES-CBC3-SHA:168)
	(WEB.DE 4.101 #44)
	id 1BhtUq-0008Tf-00; Tue, 06 Jul 2004 19:12:44 +0200
From: Martin <nakal@web.de>
To: Bill Moran <wmoran@potentialtech.com>
In-Reply-To: <20040706084256.1fb5e775.wmoran@potentialtech.com>
References: <1089094675.1206.23.camel@klotz.local>
	 <20040706084256.1fb5e775.wmoran@potentialtech.com>
Content-Type: text/plain
Message-Id: <1089133961.788.13.camel@klotz.local>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.6 
Date: Tue, 06 Jul 2004 19:12:42 +0200
Content-Transfer-Encoding: 7bit
Sender: nakal@web.de
cc: FreeBSD Questions <freebsd-questions@freebsd.org>
Subject: Re: When named is not available
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Jul 2004 17:12:48 -0000


First, I've found a solution. The nsswitch.conf file is helpful
for my scenario. You can set "hosts: files dns" and the timeouts
will never happen.

Am Tue, den 06.07.2004 schrieb Bill Moran um 14:42:

> It's a standard timeout.  The resolver isn't aware of the status of parts
> of the network stack below it ... it just waits for 30 seconds for a reply
> and then gives up if none comes.

It actually sends more queries than just one. That's why it takes that
long.

> Make sure that /etc/hosts has every possible name for your machine in it,
> in addition to "localhost".  Any time I've seen one of those WMs get hung
> up on DNS, it was becuase it was trying to verify its own host name.

I don't expect any traffic when using X-apps locally and while TCP is
switched off.

Martin