Just for fun I looked up century link's primary dns address, pointed nslookup to it as the server, and I was able to resolve google.com just fine. It seems to me that it would be extremely odd for a company to block a route to a destination rather than simply block it from dns. So I am slightly suspicious that the culprit is century link here. On Fri, Aug 29, 2014 at 11:26 AM, David Wagle <david.wagle at gmail.com> wrote: > What do you mean by "can't even be reached?" > > Is it not responding to a ping? Or are you trying to go there in a > browser? It won't show up in a browser as it's not a web server, it is a > public nameserver. > > > On Fri, Aug 29, 2014 at 10:33 AM, gregrwm <tclug1 at whitleymott.net> wrote: > >> > change your nameserver to 8.8.8.8 >> > you'll have no trouble finding google ever again. >> >> nice idea but it seems to be a connectivity issue, 8.8.8.8 can't even >> be reached, so trying to use it for nameservice just puts dns out of >> reach also. >> _______________________________________________ >> TCLUG Mailing List - Minneapolis/St. Paul, Minnesota >> tclug-list at mn-linux.org >> http://mailman.mn-linux.org/mailman/listinfo/tclug-list >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mailman.mn-linux.org/pipermail/tclug-list/attachments/20140829/9b629896/attachment.html>