From owner-freebsd-current@FreeBSD.ORG Sun Oct 22 11:54:20 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 1F53616A56B; Sun, 22 Oct 2006 11:54:20 +0000 (UTC) (envelope-from andy@athame.co.uk) Received: from hex.athame.co.uk (salama58.adsl.netsonic.fi [81.17.207.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2DA35440FB; Sun, 22 Oct 2006 11:22:21 +0000 (GMT) (envelope-from andy@athame.co.uk) Received: from ping.int.athame.co.uk ([192.168.10.8]) by hex.athame.co.uk with esmtp (Exim 4.62 (FreeBSD)) (envelope-from ) id 1GbbPF-000AoE-Jz; Sun, 22 Oct 2006 14:22:17 +0300 From: Andy Fawcett To: freebsd-current@freebsd.org Date: Sun, 22 Oct 2006 14:23:18 +0300 User-Agent: KMail/1.9.4 References: <20061022095811.GA10743@zaphod.nitro.dk> <1161515330.751.9.camel@localhost> In-Reply-To: <1161515330.751.9.camel@localhost> X-Face: ?fLK282oT!Ss!(krp%ft%TWfrkz*Mxz<2hwkRBzd); #D/=!=XjYKFBh1wVeov4K&<=?utf-8?q?Z6bi=5F=0A=09=7BBvAjk1diod2?=,DQo`Xz<\$~fX7B>U`u0HC\Gc+B9Hxu"bjBc16tg~i4.,2A1>=?utf-8?q?=7BrcRK=5Fi!i=0A=097e79f=7CT=3B9=23gfr=3DG1u=27xS=3D?=(}_NSP,Gs>HDq Cc: Hajimu UMEMOTO , "Simon L. Nielsen" , Joel Dahl 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:54:20 -0000 On Sunday 22 October 2006 14:08, Joel Dahl wrote: > 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. I'm seeing similar on one 6.x box here from time to time: $ uname -a FreeBSD ping.int.athame.co.uk 6.1-STABLE FreeBSD 6.1-STABLE #2: Mon Jul 31 02:25:05 EEST 2006 root@ping.int.athame.co.uk:/usr/obj/usr/src/sys/PING amd64 As with Simon's original report, trying again seems to work okay. I'm only seeing this effect (or maybe only noticing it) with csup/cvsup. Could be coincidence though. A. -- Andy Fawcett | andy@athame.co.uk | tap@kde.org "In an open world without walls and fences, | tap@lspace.org we wouldn't need Windows and Gates." -- anon | tap@fruitsalad.org