In article <RkULc.107992$eO.5821@edtnps89>,
Neil Morrison <nowrite@to.me> wrote:
>
>"Bill Vermillion" <bv@wjv.com> wrote in message news:I19E6z.24s7@wjv.com...
>
>> In email with the OP I got him connected. It definately appears
>> to be a problem with his ISP's DNS, as I pointed him to a DNS I
>> maintain and he was able to get what he wanted.

>> There are a lot of poorly configured DNS machines out there.

>That's for sure. Sometimes you need the IP address to connect. But my
>current ISP seems to have it working OK.

I found out the name servers he is using.

They resolve the www.sco.com to 127.0.0.1.

The nameservers are listed as the local nameservers.

I've never seen anyone screw up a DNS like that before. My gut
reaction is that someone at that ISP is part of the anti-sco group
so that no one can get to SCO for whom they provided services.

Queries for caldera.com don't even return an IP address, but
return the list of the top level domain root servers A thru M.

I may be wrong, but I can see no way someone could accidentally do
that.

Bill

--
Bill Vermillion - bv @ wjv . com