From owner-freebsd-questions@FreeBSD.ORG Wed Oct 29 22:36:16 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 7D2D31065675; Wed, 29 Oct 2008 22:36:16 +0000 (UTC) (envelope-from fbsd06+3F=fdf8ebd4@mlists.homeunix.com) Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by mx1.freebsd.org (Postfix) with ESMTP id 371F08FC1C; Wed, 29 Oct 2008 22:36:16 +0000 (UTC) (envelope-from fbsd06+3F=fdf8ebd4@mlists.homeunix.com) 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 D543ED05B1; Wed, 29 Oct 2008 18:36:14 -0400 (EDT) Date: Wed, 29 Oct 2008 22:36:12 +0000 From: RW To: freebsd-questions@freebsd.org Message-ID: <20081029223612.6da7b36e@gumby.homeunix.com> In-Reply-To: References: 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 Cc: Colin Percival Subject: Re: freebsd-update "can't find update.FreeBSD.org" 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: Wed, 29 Oct 2008 22:36:16 -0000 On Wed, 29 Oct 2008 14:25:06 -0600 "Steven Susbauer" wrote: > andrew clarke wrote: > >On Wed 2008-10-29 13:37:11 UTC-0600, Steven Susbauer > >(stupendoussteve@hotmail.com) wrote: > > > >>freebsd-update fetch fails if the default "ServerName > >>update.FreeBSD.org" is not changed to "ServerName > >>update1.FreeBSD.org" in /etc/freebsd-update.conf. > > > >>thinkpad# freebsd-update --debug fetch > >>Looking up update.FreeBSD.org mirrors... none found. > > > >May be related to this: > > > >http://lists.freebsd.org/pipermail/freebsd-questions/2008-October/183886.html > > > Yes it certainly was, my router dnsmasq.conf included filterwin2k, > which apparently blocks SRV requests. Will remember to keep that off > in the future. I think it would still be a good idea to file a PR. With portsnap the default server is itself one of the servers on the SRV list, so portsnap should fall-back to a working server even when DNS is unavailable (behind a proxy) or screwed-up by a router etc. I dont see a reason why update.FreeBSD.org shouldn't have the same A-record as update1.FreeBSD.org, so that it "just works".