Date: Wed, 18 May 2005 20:38:33 +1000 From: "Gavin R. Putland" <gavp@westnet.com.au> To: freebsd-questions@freebsd.org Subject: Re: Main web site... & egg on my face Message-ID: <200505182038.33536.gavp@westnet.com.au> In-Reply-To: <20050518014034.U62516@mail.goinet.com> References: <200505181520.23507.brainiac@westnet.com.au> <200505181633.11251.gavp@westnet.com.au> <20050518014034.U62516@mail.goinet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Ahem...
On Wed, 18 May 2005 04:41 pm, Tony Shadwick wrote:
> Just out of curiousity...
>
> cat /etc/resolv.conf
That gives the local primary and secondary nameservers of
my ISP, as I believe it should. The problem was not likely
to be in my machine because I have done a few OS installs
in recent days, whereas www.freebsd.org and the underlying
releng pages, as seen by me, are several months old.
I was familiar with resolv.conf, but not the following:
> nslookup www.freebsd.org
That gives:
Server: 203.21.20.20
Address: 203.21.20.20#53
Non-authoritative answer:
Name: www.freebsd.org
Address: 216.136.204.117
The "Server" is my ISP's primary nameserver. I don't know
the significance of the #53, but I can report that it has
been consistent for a couple of hours. When I load
216.136.204.117 into a browser, I get the UP-TO-DATE
FreeBSD home page.
That suggested to me that my ISP uses a proxy which can be
bypassed by typing the real IP address instead of the
mnemonic version thereof. So I got on a bus, went to an
internet cafe and, having established that the cafe didn't
use the same ISP, typed in www.freebsd.org... and got the
up-to-date version.
So I'll take up the matter with my ISP. (Or perhaps I
should change to internode.on.net, whose servers apparently
run FreeBSD.)
> :)
Indeed.
With thanks (and apologies, if amusement is outweighed by
annoyance).
Gavin R. Putland.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200505182038.33536.gavp>