said by Rakeesh:I really don't think Cox is doing IP level blocking of anything (in fact, I haven't heard of any domestic consumer facing ISPs that do any kind of IP level blocking of public addresses.)
I don't think they are doing DNS blocking of anything either, though they DO have flaky DNS servers (I remember one time they had an entire day where DNS servers were down due to a routing loop, and routing loops are usually a pretty easy thing to find and fix; shouldn't take a whole day.)
There are even times when I have tried to reach a subdomain which at certain times of the day, Cox's DNS servers can't resolve, whereas other DNS servers can. Interestingly, Level 3's DNS servers can't resolve them either, and Cox's DNS servers are sourced from Level 3 (anycast address of 4.2.2.1, guessing mine resides in Arizona, so it may be different elsewhere.)
What you might be running into is DNS poisoning. It's possible that your gateway device (router as most people call it, though it's actually multiple devices in one) has an internal DNS server that has a poisoned cache, or even a poisoned hosts file.
Or worse, it's possible that your client machine has a poisoned hosts file.
I looked at my hosts file and nothing is in there relating to cgpeers.com or torrentcrazy.com. I can load cgpeers.com now due to hunting it being blocked by a malware program i have running, but i didn't know it was blocking it. However, torrentcrazy.com won't load even if I shut down all of my malware/AV apps. flushed dnscache. Not sure where to look at this point.
