And yes, it's possible that your ISP straight blocks these servers. For example, if you're forced to browse behind a transparent HTTP proxy, by design you'd be using their DNS servers regardless of the "network connections" settings.
There's a simple method to check this:
- Go to Start -> Run -> type cmd and press ENTER.
- Type:
and press ENTER:
- if telnet freezes at "connecting to 1.1.1.1"... you're not behind a transparent proxy.
- if you see a black screen for like 20 seconds, and then something about having disconnected from the host, then you are behind a transparent proxy.
For the latter case, this happens because the proxy catches
all connections going to port 80 somewhere (you -> proxy -> host), and
then checks if the actual IP you're connecting to is valid or not.
I have once been behind one such proxy. It was frustrating, since my idiotic ISP had set it to cache
everything to save bandwidth and avoid buying new equipment. I could solve this by using my scripts to find and reclaim IPs that weren't affected.
Bookmarks