My internet is broken.
I have been a regular reader for the blog www.wouldashoulda.com for over two years now. About four days ago it stopped loading claiming “The server at wouldashoulda is taking too long to respond.” I tried repeatedly over the next couple of days and found several other sites that seemed gone as well. But then I discovered that other people are able to see them just fine. Nothing is broken on my end. Nothing is broken on wouldashoulda. Somewhere in the middle is a blockage. I’ve no idea why or how to fix it. My best hope is to call my ISP on Monday, but I don’t hold out much hope of them being particularly helpful.
Sigh. I miss my blog reading.
Have you tried dumping your cache? I once had a computer do that to me–Yahoo wouldn’t load of all things. But it turned out my cache was too full, and I dumped it and all was well.
DNS issues and you
You type in http://www.wouldashoulda.com
your PC queries the DNS server you are set up to use, or the one your ISP has assigned to you. It talks to other DNS servers and says, oh, http://www.wouldashoulda.com really means 208.80.252.172
All websites are actually web servers with an ip address, or a sub directory of a larger server. The DNS servers let the nice small www. address send you to whatever the numeric address is at any given moment. You need to use the command promt command ipconfig/flushdns, or have someone else do this. You may also need to have someone set you up with a list of manually entered DNS servers on your pc, so that when your local friendly ISP has DNS issues in the future, they do not affect you.
For pcs with kid usage, I often help people set their pcs up to use http://www.scrubit.com/ for DNS services. They provide a ‘scrubbed up’ version of the Internet for younger kids, simply not allowing questionable site to load.
Re: DNS issues and you
Nope!
I already checked DNS several times, from different machines here in our home. Our DNS server and a free DNS web lookup tool both provide the address you listed.
That IP address takes too long to respond. From a CMD prompt, tracert to that address times out on the first hop. Somewhere between Comcast in Utah and that address there is a router (or SOMETHING) that is failing to pass packets back and forth.
So sad.
Do what people in China do:
http://www.bbc.co.uk/doctorwho/s4/videos/S4_09?episode=S4_09&character=&action=videostream&playlist=/doctorwho/playlists/s4_09/video/s4_09_trl_03.xml&video=1&date=&summary=The%20next%20time%20preview%20for%20Midnight.&info=&info2=&info3=&tag_file_id=s4_09_trl_03
http://www.xroxy.com/proxylist.htm seems easiest.
Type in your url in the top right hand form and click go.
Batta bing, batta boom – instant new route to the site.
Re: DNS issues and you
ugh, I HATE issues with higher level network stuff. Here at least in good old North Carolina i have rarely seen backbone issues, so keeping all my stuff set up with non local DNS has made most local stuff a non issue for me. Good luck with the wait for somebody up the chain to fix it. That said, have you tried using a proxy to get around it entirely?
You are my hero! That works. I can now do an end run around whatever weird internet blockage haunts my connection. Thanks!