From owner-freebsd-hubs@FreeBSD.ORG Thu Oct 26 20:16:04 2006 Return-Path: X-Original-To: freebsd-hubs@FreeBSD.org Delivered-To: freebsd-hubs@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3345B16A407 for ; Thu, 26 Oct 2006 20:16:04 +0000 (UTC) (envelope-from eazybsd@yahoo.com) Received: from web57910.mail.re3.yahoo.com (web57910.mail.re3.yahoo.com [68.142.236.103]) by mx1.FreeBSD.org (Postfix) with SMTP id 7F1BC43D58 for ; Thu, 26 Oct 2006 20:16:03 +0000 (GMT) (envelope-from eazybsd@yahoo.com) Received: (qmail 12179 invoked by uid 60001); 26 Oct 2006 20:16:02 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding; b=HG06mRCR7R/6LyocLQOmeECGW3VPYYkp9FOdItQZlwafnX+CNK3OlDmyWoUGCJ9cLwoJXyjbsWk8VRDC+bFb0+qUnrcObfZmOpokbRvVu1d+PO5agO7T42CkH5dzlscIA6vovKRNK9+J52M2zBOJ6ZPrRZH/QwgwoU35nfO7qXU= ; Message-ID: <20061026201602.12177.qmail@web57910.mail.re3.yahoo.com> Received: from [65.189.183.148] by web57910.mail.re3.yahoo.com via HTTP; Thu, 26 Oct 2006 13:16:02 PDT Date: Thu, 26 Oct 2006 13:16:02 -0700 (PDT) From: eazy bsd To: freebsd-hubs@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailman-Approved-At: Fri, 27 Oct 2006 03:05:49 +0000 Cc: bug-followup@FreeBSD.org Subject: Re: misc/103814: cvsup11.freebsd.org dns issues X-BeenThere: freebsd-hubs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "FreeBSD Distributions Hubs: mail sup ftp" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Oct 2006 20:16:04 -0000 > ns1.downloadtech.com is causing the problem. no. cvsupx.freebsd.org are all cnames to some other fqdn that is not in freebsd.org. this is a perfectly good way to do it as it lets the host org move things around at will without coordinating such triviality with hub@. the freebsd.org nameservers are happily returning cname results [non-recursive] as per the extent of their programmed authority. as an aside, perhaps these should also use that format: cvsup2.us IN A 130.94.149.166 cvsup7.us IN A 129.250.31.140 cvsup3.pt IN A 193.136.165.121 now back to the problem. when asked to recursively resolve the cvsup11 cname to an A record, or to do so via multiple finer grained queries... resolvers and nameservers [including freebsd.org. authoritative ones such as downloadtech if asked] will timeout because the uu.net records do not resolve as per the pr. the solution is any of: contact uu ;-] ignore it, cvsup to the ip, embrace uncertainty ;-[ find another mirror as good as cvsup11 ;-| as for contacting uu, there's no historical reference to 'cvsup11|research\.uu\.net' in the entire mail archive so no help there. failing others, try hostmaster@uu.net as listed in the uu.net soa. if someone does contact uu, let them know that of the three authoritative servers for research.uu.net listed in uu.net, the two authxx ones below do not seem to be carrying its records either. so if they're just caches and beast goes away, ergo research after a while. uu.net zone is missing glue to beast.research as well. @auth00 research.uu.net. IN NS beast.research.uu.net. research.uu.net. IN NS auth03.ns.uu.net. research.uu.net. IN NS auth50.ns.uu.net. the reverse part has been omitted. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com