It's so ... entertaining, to be able to use some sites and not others. (due to relying on DNS caching)
===============
C:\Windows\System32>nslookup - 205.171.3.66
Default Server: redirect.centurytel.net
Address: 205.171.3.66
> google.com
Server: redirect.centurytel.net
Address: 205.171.3.66
*** redirect.centurytel.net can't find google.com: Server failed
================
C:\Windows\System32>nslookup - 205.171.202.166
Default Server: redirect.centurytel.net
Address: 205.171.202.166
> google.com
Server: redirect.centurytel.net
Address: 205.171.202.166
DNS request timed out.
timeout was 2 seconds.
*** redirect.centurytel.net can't find google.com: Server failed
================
Let's try Google's public DNS. Odd, doesn't work. Almost as if CenturyLink is blocking it or something.
C:\Windows\System32>nslookup - 8.8.8.8
DNS request timed out.
timeout was 2 seconds.
Default Server: UnKnown
Address: 8.8.8.8
> google.com
Server: UnKnown
Address: 8.8.8.8
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out
================
Oh well I next used Windows Remote Desktop to connect to my work computer, which I can do because I know it's numeric address. Works great, no problems, pops right open, I'm now on my server room desktop computer at work.
================
And now let's try Google's public DNS again at work:
C:\Windows\System32>nslookup - 8.8.8.8
Default Server: google-public-dns-a.google.com
Address: 8.8.8.8
> google.com
Server: google-public-dns-a.google.com
Address: 8.8.8.8
Non-authoritative answer:
Name: google.com
Addresses: 2607:f8b0:4009:808::200e
205.213.114.29
205.213.114.30
205.213.114.44
205.213.114.42
205.213.114.57
205.213.114.27
205.213.114.53
205.213.114.59
205.213.114.49
205.213.114.45
205.213.114.19
205.213.114.38
205.213.114.34
205.213.114.23
205.213.114.15
Looky that, works great. It's almost as if CenturyLink is blocking my access to Google's 8.8.8.8 public DNS from my home CenturyLink DSL? Naw, couldn't be.
=======================
*Opens a 128k music stream from home DSL, in windows media player, using IP address*
http://74.217.192.202/wma128/groovesalad.asx
That works great too, so it's not a bandwidth problem.
Anyway, that's some lovely network reliability you got there CenturyLink.
--
CenturyLink remote pedestal: RUBY, 10 miles west of Gilman, WI
http://www.dslreports.com/forum/r20533172-Rural-Century-Telephone-remote-terminal-unit
http://www.dslreports.com/forum/r20530745-Name-of-this-polemount-outdoor-telco-canister
↧