Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 22 Apr 2008 17:50:02 +1000
From:      andrew clarke <mail@ozzmosis.com>
To:        freebsd-questions@freebsd.org
Subject:   Re: Looking up portsnap.FreeBSD.org mirrors... none found.
Message-ID:  <20080422075002.GA24281@ozzmosis.com>
In-Reply-To: <20080421214038.GA80334@ozzmosis.com>
References:  <20080421214038.GA80334@ozzmosis.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue 2008-04-22 07:40:38 UTC+1000, andrew clarke (mail@ozzmosis.com) wrote:

> I have serveral FreeBSD machines on my home network and was wondering
> why Portsnap failed to find any mirrors on some but not others.  I had
> a look at the /usr/sbin/portsnap script to find out what it is doing.
> The command it calls to search for mirrors is:
> 
> host -t srv _http._tcp.portsnap.freebsd.org
> 
> resulting in:
> 
> ;; connection timed out; no servers could be reached
> 
> After a bit of investigating it turns out that on the machines where
> it failed, /etc/resolv.conf was configured to use my D-Link DSL-504T
> ADSL modem/router's internal nameserver for DNS lookups.  Changing
> resolv.conf to instead point directly at my ISP's nameservers solved
> the problem.

Just a short update to this.  The DSL-504T runs embedded Linux, using
dproxy as a caching name server.  So it would as though dproxy does
not support SRV record lookups.

Interestingly, dproxy isn't in the FreeBSD Ports tree.

http://www.dlink.com.au/Products.aspx?Sec=1&Sub1=1&Sub2=2&PID=49
http://dproxy.sourceforge.net/
http://en.wikipedia.org/wiki/SRV_record



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080422075002.GA24281>