On 04/18/2013 01:08 PM, Eduardo Morras wrote:
> On Thu, 18 Apr 2013 20:35:37 +1000
> Chris Angelico <rosuav@gmail.com> wrote:
>
>> That one's clearly fine. What about www.postgresql.org? It's possible
>> you have a poisoned cache for just that one record.
>>
>> ChrisA
>
> I have clean all (dns, web cache, etc) and get:
>
> camibar% nslookup www.postgresql.org
> Server: 62.42.230.24
> Address: 62.42.230.24#53
>
> Non-authoritative answer:
> www.postgresql.org canonical name = www.mirrors.postgresql.org.
> Name: www.mirrors.postgresql.org
> Address: 87.238.57.232
> Name: www.mirrors.postgresql.org
> Address: 98.129.198.126
> Name: www.mirrors.postgresql.org
> Address: 217.196.149.50
those are the correct IPv4-adddresses of all currently active postgresql
web frontends.
>
> In 87.238.57.232 (Sweeden) 98.129.198.126(San Antonio,TX) and 217.196.149.50(Saltzburg) i get lighttpd default page.
this is expected if you are not sending a http host header for one of
our domains.
Stefan
