If you're still experiencing problems, a traceroute (tracert) to our domain (using the hostname speedguide.net, or one of the IPs, 63.217.30.70, 63.217.30.71) would be appreciated.
Also, for those having problems... Can you also try the following in command prompt:
nslookup speedguide.net
Can you access the site using the IP address, rather than the hostname (as in: http://63.217.30.71 ) ?
TIA
Update:
I've talked to the NOC and there are no problems with any backbones they're aware of, our server is up and running without any load issues as well. The problem seems to be DNS related, our host name not being resolved to the right IP at times for some users... I am not sure who is affected at this time.
We're using external name servers (from our domain registrar), and they seem to be resolving the hostname correctly... If you're still experiencing problems, please let me know and try both the following in command prompt:
nslookup speedguide.net
nslookup speedguide.net ns1.nameresolve.com
If the site speedguide.net resolves to anything but 63.217.30.70, you are not going to be able to accessing (using the domain name, just by using the IPs: http://63.217.30.70 for the main site, http://63.217.30.71 for the forums).
If you see: wc.traffic.puredns.com / wc.funnel.revenuedirect.com.akadns.net anywhere in the nslookup results, they're some alternate domain parking redirects, I'm not sure if used by Google or Dotster...
Update 2:
And here is the culprit... Seems Dotster "accidently" redirected all their customers' websites to a parking page full of ads temporarily, including SG... And depending on how long your ISP's DNS servers cache the information, you might still be experiencing the aftereffects. Here is all we got from them, GRR:
Dotster wrote: DNS Issues:
We experienced a temporary DNS issue last night that caused some web sites to forward to a Parked page. This problem was resolved immediately after it was discovered. The DNS issue has been corrected but some customers are still reporting downtime. This downtime is due to the caching of their ISP. Once the ISP updates their DNS Records, all sites should be operational.
Posted by Customer Care - 04/6/2006@10:51