From owner-freebsd-current@FreeBSD.ORG Tue Oct 24 04:49:05 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3D81216A492 for ; Tue, 24 Oct 2006 04:49:05 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.FreeBSD.org (Postfix) with SMTP id B950B43D6B for ; Tue, 24 Oct 2006 04:49:02 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 32254 invoked by uid 399); 24 Oct 2006 04:49:02 -0000 Received: from localhost (HELO ?192.168.0.4?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 24 Oct 2006 04:49:02 -0000 Message-ID: <453D9B3B.5090000@FreeBSD.org> Date: Mon, 23 Oct 2006 21:48:59 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: Jiawei Ye References: <20061022095811.GA10743@zaphod.nitro.dk> <1161515330.751.9.camel@localhost> <200610221423.19817.andy@athame.co.uk> <453BFC2A.5010501@FreeBSD.org> <20061023022928.35b7b23c@it.buh.tecnik93.com> <20061024021919.GA74370@xor.obsecurity.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: UMEMOTO , Kris Kennaway , "Simon L. Nielsen" , freebsd-current@freebsd.org, Joel@freebsd.org, Ion-Mihai IOnut Tetcu , Hajimu@freebsd.org Subject: Re: Resolver not always resolving hostnames X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Oct 2006 04:49:05 -0000 Jiawei Ye wrote: > On 10/24/06, Kris Kennaway wrote: >> On Tue, Oct 24, 2006 at 09:50:56AM +0800, Jiawei Ye wrote: >> >> > I am still seeing this on a fairly recent -current >> >> With the patch applied? >> >> Kris > With "options attempts:4" in resolv.conf Try applying the patch, and commenting out the options line. The patch fixes things in what should be a more robust way. Doug -- This .signature sanitized for your protection