RE: [cobalt-users] Strange HTTP Problem

["Simon Pierce" <simon@xxxxxxxxxxxxxxx>]

>First tell your customer to flush their cache in Internet Explorer or
>Netscape (assuming they are using it)
>Then you check your zone files to make sure you have the proper mx records
>for the ip assignment to domain name. Also, if you can ping the ip and not
>domain, check with whois servers to see if they have been held for
>non-payment of domain name.
>Just some thoughts..
>Tom

The only issue here is HTTP requests timing out when sent through one
particular ISP. No other abnormalities, and it effects all domain names and
IPs on the server. I checked it myself by dialling up to the ISP in
question, and there are no end-user problems such as caching.

Si