Date: Sun, 22 Oct 2006 14:23:18 +0300 From: Andy Fawcett <andy@athame.co.uk> To: freebsd-current@freebsd.org Cc: Hajimu UMEMOTO <ume@freebsd.org>, "Simon L. Nielsen" <simon@freebsd.org>, Joel Dahl <joel@freebsd.org> Subject: Re: Resolver not always resolving hostnames Message-ID: <200610221423.19817.andy@athame.co.uk> In-Reply-To: <1161515330.751.9.camel@localhost> References: <20061022095811.GA10743@zaphod.nitro.dk> <ygeiriczkir.wl%ume@mahoroba.org> <1161515330.751.9.camel@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
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" <simon@FreeBSD.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200610221423.19817.andy>