From owner-freebsd-questions@FreeBSD.ORG Tue Oct 7 14:53:10 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E98C91065697 for ; Tue, 7 Oct 2008 14:53:10 +0000 (UTC) (envelope-from fbsd06+2P=f0485365@mlists.homeunix.com) Received: from fallback-in1.mxes.net (fallback-out1.mxes.net [216.86.168.190]) by mx1.freebsd.org (Postfix) with ESMTP id 70D358FC08 for ; Tue, 7 Oct 2008 14:53:10 +0000 (UTC) (envelope-from fbsd06+2P=f0485365@mlists.homeunix.com) Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by fallback-in1.mxes.net (Postfix) with ESMTP id D5C0B164668 for ; Tue, 7 Oct 2008 10:41:39 -0400 (EDT) Received: from gumby.homeunix.com. (unknown [87.81.140.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTP id 41CDED05B8 for ; Tue, 7 Oct 2008 10:41:38 -0400 (EDT) Date: Tue, 7 Oct 2008 15:41:35 +0100 From: RW To: freebsd-questions@freebsd.org Message-ID: <20081007154135.535dbd12@gumby.homeunix.com.> In-Reply-To: <20081007075524.GA72002@mavetju.org> References: <94136a2c0810060139r740c3a96hc9c79028e7b93a4d@mail.gmail.com> <20081007075524.GA72002@mavetju.org> X-Mailer: Claws Mail 3.5.0 (GTK+ 2.12.11; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: update.FreeBSD.org / No mirrors remaining, giving up X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Oct 2008 14:53:11 -0000 On Tue, 7 Oct 2008 18:55:24 +1100 Edwin Groothuis wrote: > > $ freebsd-update fetch > > Fetching metadata signature for 7.0-RELEASE from > > update.FreeBSD.org... failed. No mirrors remaining, giving up. > > I've heard this before and it is caused by resolvers (most likely > your router?) which don't understand requests for SRV records. freebsd-update and portsnap should fall back to the configured server if they can't get SRV records, they should be able to work through an http-proxy without any DNS access at all on the local machine. It sounds like a bug if SRV records are needed.