From owner-freebsd-current@FreeBSD.ORG Sun Oct 22 11:08:57 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 CAF8516A40F; Sun, 22 Oct 2006 11:08:57 +0000 (UTC) (envelope-from joel@FreeBSD.org) Received: from av7-2-sn3.vrr.skanova.net (av7-2-sn3.vrr.skanova.net [81.228.9.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4841143D5C; Sun, 22 Oct 2006 11:08:52 +0000 (GMT) (envelope-from joel@FreeBSD.org) Received: by av7-2-sn3.vrr.skanova.net (Postfix, from userid 502) id A3D3D37ED0; Sun, 22 Oct 2006 13:08:38 +0200 (CEST) Received: from smtp3-2-sn3.vrr.skanova.net (smtp3-2-sn3.vrr.skanova.net [81.228.9.102]) by av7-2-sn3.vrr.skanova.net (Postfix) with ESMTP id 8EC6F37E43; Sun, 22 Oct 2006 13:08:38 +0200 (CEST) Received: from dude.automatvapen.se (81-229-112-193-no21.tbcn.telia.com [81.229.112.193]) by smtp3-2-sn3.vrr.skanova.net (Postfix) with ESMTP id A457737E47; Sun, 22 Oct 2006 13:08:50 +0200 (CEST) From: Joel Dahl To: Hajimu UMEMOTO In-Reply-To: References: <20061022095811.GA10743@zaphod.nitro.dk> Content-Type: text/plain Date: Sun, 22 Oct 2006 13:08:50 +0200 Message-Id: <1161515330.751.9.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.6.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org, "Simon L. Nielsen" 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: Sun, 22 Oct 2006 11:08:57 -0000 On Sun, 2006-10-22 at 19:56 +0900, Hajimu UMEMOTO wrote: > Hi, > > >>>>> On Sun, 22 Oct 2006 11:58:12 +0200 > >>>>> "Simon L. Nielsen" said: > > simon> Initially I thought it was a local problem for me, but joel@ has seen > simon> the same on RELENG_6 (from July 8), and xride@ has seen the > simon> same/similar with csup where his workaround was to ping the cvsup > simon> server before running csup. > > Is the date correct? Since I did MFC BIND9's resolver into RELENG_6 > at July 17, this issue seems not related to resolver update. Yes, the date is correct. Also, itetcu@ is seeing the same thing with a RELENG_6 from June, so I guess your MFC isn't responsible for this. -- Joel