From owner-freebsd-current@FreeBSD.ORG Sun Oct 22 10:06:24 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 B153516A40F for ; Sun, 22 Oct 2006 10:06:24 +0000 (UTC) (envelope-from joel@FreeBSD.org) Received: from av10-2-sn2.hy.skanova.net (av10-2-sn2.hy.skanova.net [81.228.8.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id F235443D6A for ; Sun, 22 Oct 2006 10:06:14 +0000 (GMT) (envelope-from joel@FreeBSD.org) Received: by av10-2-sn2.hy.skanova.net (Postfix, from userid 502) id 8768E37F63; Sun, 22 Oct 2006 12:06:11 +0200 (CEST) Received: from smtp4-1-sn2.hy.skanova.net (smtp4-1-sn2.hy.skanova.net [81.228.8.92]) by av10-2-sn2.hy.skanova.net (Postfix) with ESMTP id 67E8837E4E; Sun, 22 Oct 2006 12:06:11 +0200 (CEST) Received: from dude.automatvapen.se (81-229-112-193-no21.tbcn.telia.com [81.229.112.193]) by smtp4-1-sn2.hy.skanova.net (Postfix) with ESMTP id 4B76337E6F; Sun, 22 Oct 2006 12:06:11 +0200 (CEST) From: Joel Dahl To: "Simon L. Nielsen" In-Reply-To: <20061022095811.GA10743@zaphod.nitro.dk> References: <20061022095811.GA10743@zaphod.nitro.dk> Content-Type: text/plain Date: Sun, 22 Oct 2006 12:06:10 +0200 Message-Id: <1161511570.751.5.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, Hajimu UMEMOTO 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 10:06:24 -0000 On Sun, 2006-10-22 at 11:58 +0200, Simon L. Nielsen wrote: > Hey, > > 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. > > I see it on recent -CURRNET's (server running cvsup below is October > 12, system running host(1) is October 15). > > The cvsup log: > > 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 > > 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. > > $ 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. > > I only have one name-server in resolv.conf, so the problem isn't due > to hitting different caching name-servers. > > 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. I could reproduce this quite easily on current a couple of days ago, running cvsup resulted in "Name lookup failure for cvsup.no.freebsd.org": Host name lookup failed" about (approximately) every other time I ran it. -- Joel