Re: Resolver not always resolving hostnames

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_at_FreeBSD.org> said:
> >
> > simon> Initially I thought it was a local problem for me, but joel_at_
> > has seen simon> the same on RELENG_6 (from July 8), and xride_at_ 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_at_ 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_at_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_at_athame.co.uk
                                                 | tap_at_kde.org
"In an open world without walls and fences,      | tap_at_lspace.org
  we wouldn't need Windows and Gates."  -- anon  | tap_at_fruitsalad.org