Date: Tue, 02 Nov 2010 13:48:12 +0000 From: Vincent Hoffman <vince@unsane.co.uk> To: freebsd-questions@freebsd.org Subject: Re: Continuing problem with "portsnap" Message-ID: <4CD0169C.5070207@unsane.co.uk> In-Reply-To: <20101102093707.60a2bd0c@scorpio> References: <20101102073440.5b7f6e74@scorpio> <4CCFF82A.8080905@unsane.co.uk> <4CCFF983.4020005@eskk.nu> <20101102082136.34dfd94d@scorpio> <AANLkTik=0f_8eN%2B=Z6LqdMkPzX5%2Bun8DrGh04xBrttf5@mail.gmail.com> <20101102093707.60a2bd0c@scorpio>
next in thread | previous in thread | raw e-mail | index | archive | help
On 02/11/2010 13:37, Jerry wrote: > On Tue, 2 Nov 2010 05:32:44 -0700 > Rob Farmer <rfarmer@predatorlabs.net> articulated: > >> >> This is a separate issue due to bad DNS - the list of mirrors is >> obtained from: >> >> host -t srv _http._tcp.portsnap.freebsd.org >> >> and falls back to just portsnap.freebsd.org if it doesn't work. > Results: > > $ fetch http://portsnap1.freebsd.org/pub.ssl > fetch: http://portsnap1.freebsd.org/pub.ssl: No address record > > $ fetch http://portsnap1.freebsd.org/snapshot.ssl > fetch: http://portsnap1.freebsd.org/snapshot.ssl: No address record > > $ host -t srv _http._tcp.portsnap.freebsd.org > ;; connection timed out; no servers could be reached > > Yes, I would say that something is broken somewhere, I just am not sure > where. > Sounds like DNS to me. what output do you get from dig +trace portsnap.freebsd.org Vince
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4CD0169C.5070207>