As many of you know, on February 1 I had the site for SlashdotReview.com migrated to a newly provisioned server, in order to allow me to upgrade to the new version of WordPress.
The transition went relatively smoothly, but I have been getting puzzling emails from various listeners who have not been able to get to the site.
First, I thought it was a problem with some cached DNS information from the old site, but now I am not so sure.
Could some of you with networking experience let me know what you think is going on, and how we can get these folks back in business ?
Here’s a message from Atlanta:
Hello Andy,
I have been having a problem getting to your site for a couple of weeks now.
It works from the day job @HP (15.x.x.x) but not from home or from a
couple of other customer networks that I support. All the other sites
I visit work fine from all locations.I did a few traceroutes from the different environments and I seem to
be getting hung up at 216.69.188.18 That is one hop before I get to
68.178.200.238 ( I assume this is your shared hosting server’s IP
address ). All attempts to contact port 80 work from day job but fail
from other networks.For reference you can see if you can trace back to 64.200.231.246 (
this is an Atlanta Charter networks router )Love the show,
Mike
There’s been an ongoing conversation for several days along these similar lines with another listener – at first I thought it was a Cox server problem – but this is the latest exchange
Andy:
I did a few traceroute commands to your site as well as techpodcasts and paypal. All of them failed to complete after 30 hops I then ran yours again with a 64 hop limit and it also failed. I then ran a few domains of local companies and they completed ok. I then ran a traceroute of your domain from nwtools and it completed with 30 hops.
I’ve attached the output of the traceroute’s that I did in 3 text files and a pdf file.
This is very weird. As I mentioned, I can get to techpodcasts and paypal with no problems. It is like there is a router somewhere in the chain that is not configured correctly and is sending the request into ‘bit heaven’. That is, from my entry point on the ‘net.
See if you can do a traceroute to my IP: 68.9.xxx.xxx
John
I was not able to trace back to his IP – traceroute basically giving up after about three to five hops, all * * * *
So, that’s the mystery. Probably no mystery at all to someone who does this for a living.
Please send me at email – slashdotreview at gmail
Thanks ! Have a good weekend ..