My Lesson in IP and DNS Routing

Strangest day, (24hrs) I have had in a while

We have not been able to access email or any of our sites for over 24hrs.
.
Kicker is it’s only limited to Server Node107’s IP and my ISP. Everyone else can get to the sites, except folks on my ISP.

A look at traceroute/Ping results showed the problem somewhere else down the line. I could get to other servers (node 99 and 105 tested) fine. Just not mine (node107). It has been a long and trying road.

Eventually it became clear that the fastest solution, (opposed to moving servers) was to grab a static IP. Which I then did Guy at the hosting farm forgot to move the rest of my sites (clients and our businesses) IP addresses. Result? Still can’t do anything.

Second time around we got them all changed and I am just now, 26hrs later getting email again and able to access company intranets and the like.

I was not alone apparently. The techs at the server farm said there were a spate of them going on. Routing errors, as I was told. I did some research and found it is not server specific. Meaning; I am not alone. Just a strange bug of the web. Some folks could get to a certain website from work, but not at home.

If you have a website that won’t come up for everyone, try changing the DNS. It’s probably a DNS routing error.

If you ever need a FREE traceroute and ping utility the one I found and used was http://www.pingplotter.com/download.html