Date: Wed, 29 Oct 2008 16:00:44 -0700 From: Colin Percival <cperciva@freebsd.org> To: RW <fbsd06@mlists.homeunix.com> Cc: freebsd-questions@freebsd.org Subject: Re: freebsd-update "can't find update.FreeBSD.org" Message-ID: <4908EB1C.9010601@freebsd.org> In-Reply-To: <20081029223612.6da7b36e@gumby.homeunix.com> References: <BAY122-F36E61B951A60BBEA5366E0BA260@phx.gbl> <20081029223612.6da7b36e@gumby.homeunix.com>
next in thread | previous in thread | raw e-mail | index | archive | help
RW wrote: > 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". With portsnap, I asked for the A record to be created not as a fallback for people with broken DNS, but instead as a backwards compatibility mechanism for people who were running old versions of portsnap which didn't do SRV lookups. To be honest, I didn't realize that there were so many people with broken DNS resolution. I'll ask the FreeBSD DNS admins to add an A record for update.freebsd.org. Colin Percival
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4908EB1C.9010601>