Here's an example screenshot..
The web server IS up. It's also ping-able by external sources (friends,
free proxy sites, etc).
(Attached)
On Fri, Nov 7, 2008 at 4:04 PM, olivier Thereaux <ot@w3.org> wrote:
> Hello,
>
> On 27-Oct-08, at 10:40 PM, . wrote:
>
>> 500 Can't connect to k1t.net:80 (connect: Connection refused)
>>
>> If you made recent changes to your domain name (DNS) configuration, you
>> may also want to check that your domain records are correct, or ask your
>> hosting company to do so.
>>
>>
>> This seems to only happen soon after DNS updates, so it's possible W3C is
>> w3.org is using an older cached address.
>>
>
> That's possible indeed. The validator's DNS cache, just as any computer's,
> tends to take up to a day to update.
>
> One cool trick I would try, in that case, would be, instead of checking
> http://www.example.org/
> is to check
> http://www.example.org./
> (notice the dot)
>
> Hope this helps,
> --
> olivier
>
>
>
>
