Date: Tue, 06 Jul 2004 19:12:42 +0200 From: Martin <nakal@web.de> To: Bill Moran <wmoran@potentialtech.com> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: When named is not available Message-ID: <1089133961.788.13.camel@klotz.local> In-Reply-To: <20040706084256.1fb5e775.wmoran@potentialtech.com> References: <1089094675.1206.23.camel@klotz.local> <20040706084256.1fb5e775.wmoran@potentialtech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1089133961.788.13.camel>