Date: Sun, 22 Oct 2006 13:28:22 +0300 From: Ion-Mihai "IOnut" Tetcu <itetcu@FreeBSD.org> To: Ion-Mihai "IOnut" Tetcu <itetcu@FreeBSD.org> Cc: freebsd-current@freebsd.org, Hajimu UMEMOTO <ume@FreeBSD.org>, "Simon L. Nielsen" <simon@FreeBSD.org> Subject: Re: Resolver not always resolving hostnames Message-ID: <20061022132822.417e2693@it.buh.tecnik93.com> In-Reply-To: <20061022132225.13299ae6@it.buh.tecnik93.com> References: <20061022095811.GA10743@zaphod.nitro.dk> <20061022132225.13299ae6@it.buh.tecnik93.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_CzH=DclyobdXNpM4YEu4nSO Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Sun, 22 Oct 2006 13:22:25 +0300 Ion-Mihai "IOnut" Tetcu <itetcu@FreeBSD.org> wrote: > On Sun, 22 Oct 2006 11:58:12 +0200 > "Simon L. Nielsen" <simon@FreeBSD.org> wrote: >=20 > > Hey, > >=20 > > I think something odd is going on in the resolver. It seems like it > > doesn't resolve hostnames some of the time. It's not really easily > > reproducible, but I have seen it happen several times with cvsup > > where it can't resolve the cvsup server. If I re-run cvsup it > > works fine. > >=20 > > I see it on recent -CURRNET's (server running cvsup below is October > > 12, system running host(1) is October 15). > >=20 > > The cvsup log: > >=20 > > CVSup update begins at 2006-10-18 17:29:00 > > Updating from cvsup3.dk.freebsd.org > > Name lookup failure for "cvsup3.dk.freebsd.org": Host name lookup > > failed Updating local ncvs > > CVSup update ends at 2006-10-18 17:29:01 > >=20 > > I also seen odd things happen with host(1). These two commands were > > run right after each other. I don't know if it's related, but I > > suspect it is. > >=20 > > $ host cvsup3.dk.freebsd.org > > cvsup3.dk.freebsd.org is an alias for mirror03.inet.tele.dk. > > cvsup3.dk.freebsd.org is an alias for mirror03.inet.tele.dk. > > $ host cvsup3.dk.freebsd.org > > cvsup3.dk.freebsd.org is an alias for mirror03.inet.tele.dk. > > mirror03.inet.tele.dk has address 195.41.53.219 > > cvsup3.dk.freebsd.org is an alias for mirror03.inet.tele.dk. > > cvsup3.dk.freebsd.org is an alias for mirror03.inet.tele.dk. > >=20 > > I only have one name-server in resolv.conf, so the problem isn't due > > to hitting different caching name-servers. > >=20 > > Initially I thought it was a local problem for me, but joel@ has > > seen the same on RELENG_6 (from July 8), and xride@ has seen the > > same/similar with csup where his workaround was to ping the cvsup > > server before running csup. > >=20 > > So, has anyone seen anything similar? Since I can't reproduce the > > issue at will I don't really know where to look for what's going on, > > and of course it could be DNS issue... >=20 > Seen the same, I believe it started sometime around 21 Jun in > RELEND_6. The machine in question, where I first observed this is: 6.1-STABLE #1: Fri Jun 9 13:26:04 EEST 2006 --=20 IOnut - Un^d^dregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" "Get back to your stations!" "We're beaming down to the planet, -- Kirk and Mr. Leslie, "This Side of Paradise", stardate 3417.3 --Sig_CzH=DclyobdXNpM4YEu4nSO Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFO0fGBX6fi0k6KXsRAv5MAKDGiamUq61G7w8tkpyOhS499gctpQCfWA0q e+dRoB/lclquvCZM1WPMpLg= =TVkz -----END PGP SIGNATURE----- --Sig_CzH=DclyobdXNpM4YEu4nSO--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061022132822.417e2693>