From owner-freebsd-current@FreeBSD.ORG Sun Oct 22 10:03:29 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 AD3DD16A407; Sun, 22 Oct 2006 10:03:29 +0000 (UTC) (envelope-from gabor@FreeBSD.org) Received: from server.t-hosting.hu (server.t-hosting.hu [217.20.133.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C9A843D4C; Sun, 22 Oct 2006 10:03:28 +0000 (GMT) (envelope-from gabor@FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by server.t-hosting.hu (Postfix) with ESMTP id 5FED499FBCD; Sun, 22 Oct 2006 12:03:26 +0200 (CEST) X-Virus-Scanned: amavisd-new at t-hosting.hu Received: from server.t-hosting.hu ([127.0.0.1]) by localhost (server.t-hosting.hu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id r8Gb5ruK2+79; Sun, 22 Oct 2006 12:03:25 +0200 (CEST) Received: from [192.168.2.186] (catv-50635cb6.catv.broadband.hu [80.99.92.182]) by server.t-hosting.hu (Postfix) with ESMTP id 65FBC99FB91; Sun, 22 Oct 2006 12:03:25 +0200 (CEST) Message-ID: <453B41EC.5060202@FreeBSD.org> Date: Sun, 22 Oct 2006 12:03:24 +0200 From: =?ISO-8859-1?Q?G=E1bor_K=F6vesd=E1n?= User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: "Simon L. Nielsen" References: <20061022095811.GA10743@zaphod.nitro.dk> In-Reply-To: <20061022095811.GA10743@zaphod.nitro.dk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed 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:03:29 -0000 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. > > 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... > > Same here with csup vs. cvsup.hu.FreeBSD.org. If I resolve it elsewhere and specify the ip address manually, it works just fine. Tomorrow's -current here on i386. -- Cheers, Gabor