From owner-freebsd-questions@FreeBSD.ORG Fri Feb 27 10:21:51 2004 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 DB7C816A4E2 for ; Fri, 27 Feb 2004 10:21:51 -0800 (PST) Received: from out014.verizon.net (out014pub.verizon.net [206.46.170.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id 73EF943D31 for ; Fri, 27 Feb 2004 10:21:51 -0800 (PST) (envelope-from cswiger@mac.com) Received: from mac.com ([68.161.120.219]) by out014.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20040227182150.TTUS19064.out014.verizon.net@mac.com>; Fri, 27 Feb 2004 12:21:50 -0600 Message-ID: <403F8AB0.7060403@mac.com> Date: Fri, 27 Feb 2004 13:21:36 -0500 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Barbish3@adelphia.net References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at out014.verizon.net from [68.161.120.219] at Fri, 27 Feb 2004 12:21:50 -0600 cc: Travis Troyer cc: freebsd-questions@freebsd.org Subject: Re: Problems resolving hosts X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Feb 2004 18:21:52 -0000 JJB wrote: > You are experiencing one of the many problems created by the new > file system in the 5.x development releases. The file system gets > all locked up and then times out before releasing the sector on the > hard drive so it can be read by program. Dude, Travis' problem sounds a lot more like what would happen if one of the nameservers listed in /etc/resolv.conf wasn't responding to DNS queries. Your responses would be more helpful to other people if you refrained from locking the notion that all problems with 5.x are due to UFS2 into your brain, or for that matter, being convinced that IPFW is completely broken and there is a conspiracy against other firewalls on FreeBSD. :-) -- -Chuck PS: To debug your problem, try using "dig @ns1 host", where you replace ns1 with each of the DNS resolvers you have listed or available, and replace host with one or more hostnames that have been causing delays. This will show you how quickly DNS is working and thus confirm whether the problem lies in this area, or else expose which nameserver isn't working and maybe why...