Re: ftp.sco.com not found (by my ISP)
From: Bill Vermillion (bv_at_wjv.com)
Date: Fri, 23 Jul 2004 15:25:01 GMT
In article <v%%Lc.47552$2i3.13579@clgrps12>,
Neil Morrison <email@example.com> wrote:
>"Bill Vermillion" <firstname.lastname@example.org> wrote in message news:I1A9uB.email@example.com...
>> In article <RkULc.107992$eO.5821@edtnps89>,
>> Neil Morrison <firstname.lastname@example.org> wrote:
>> >"Bill Vermillion" <email@example.com> wrote in message
>> >> 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
>I can't ping sco.com at the moment. The DNS says it's
>18.104.22.168 but it times out so I assume there's some sort of
>redirection going on. And caldera.com returns 22.214.171.124 as
>the address but the same results - no ping. However I can go to
>the web site fine! Go figure.
Many place disable ping responses to help elminate DDoS events. So
no response to ping means nothing. I've seen some places that
turn off all ICMP messaging so you can never tell what is wrong.
It's a mis-guided attempt at security IMO.
-- Bill Vermillion - bv @ wjv . com