From owner-freebsd-current@FreeBSD.ORG Sun Oct 22 09:58:15 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 2FC5D16A403; Sun, 22 Oct 2006 09:58:15 +0000 (UTC) (envelope-from simon@zaphod.nitro.dk) Received: from mx.nitro.dk (zarniwoop.nitro.dk [83.92.207.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD68343D46; Sun, 22 Oct 2006 09:58:14 +0000 (GMT) (envelope-from simon@zaphod.nitro.dk) Received: from zaphod.nitro.dk (unknown [192.168.3.39]) by mx.nitro.dk (Postfix) with ESMTP id 4C688386C0B; Sun, 22 Oct 2006 09:58:13 +0000 (UTC) Received: by zaphod.nitro.dk (Postfix, from userid 3000) id 0E29B11434; Sun, 22 Oct 2006 11:58:12 +0200 (CEST) Date: Sun, 22 Oct 2006 11:58:12 +0200 From: "Simon L. Nielsen" To: freebsd-current@freebsd.org Message-ID: <20061022095811.GA10743@zaphod.nitro.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.11 Cc: Hajimu UMEMOTO Subject: 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 09:58:15 -0000 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... -- Simon L. Nielsen