![]() is it possible they can't see it because they're at work? ie: blogger.com is filtered as a non-work-related site?
|
|
![]() At least one of them was able to comment on the blog. They went to a Google cache of one of the posts, clicked the "Comment" link, and up popped the comment page which is at blogger.com.
That means, as far as I can tell, it's something in the DNS that's not working. And I can't trace it from here, because for me it is working. --
Drew |
|
![]() The aaxnet.com site disappeared. I called OC Hosting and the support guy didn't even recognize the ocservers.com DNS servers I'd been using ever since the transfer from Velocity. He had me change them to carrierzone.com DNS servers at Network Solutions.
I could access the aaxnet.com site from my LinkLine DSL service in less than 20 minutes, but it was 3 days before I could send emails from my clovegarden.com account (hosted with HostUltra) to my aaxnet.com account. Clearly, when DNS goes screwy, it can take quite some time for the kinks to work out. |
|
![]() One report from Texas, one from Slovenia, and one from right here in Cleveland. Obviously there could be lots of other people who aren't seeing the site who aren't telling me about it.
--
Drew |
|
![]() It sounds identical to your problems, but this time with Amazon's S3:
http://developer.ama...=34076&tstart=150 [edit:] Yet more gotchas that may or may not apply: http://www.dns.net/d...tml#cname-targets Dunno if any of this is helpful. I found these links by searching on "dns cname not propagating" (without the quotes). Good luck! Cheers, Scott. |