There my be a technical problem with the blog

Expect some problems with the blog for some hours.

For those WDTPRS vets around here, remember my problems with my old hosting service over a year ago?

Apparently they didn’t do all that they were supposed to do to keep my domain registered, even though it is all paid up.

Fun huh?

I don’t know how this happened, but expect problems.

 

UPDATE: 13 March 23:24 GMT 

I am getting messages that the blog can’t be accesses right now in the UK, in Switzerland, in some places on the US eastern seaboard, in New Mexico.  However, people are getting it in the midwest and in California.

I suspect what is happening is that the BAD message is still propagating  through the internet servers, while the GOOD message is chasing it around the world.

 

 

FacebookEmailPinterestGoogle GmailShare/Bookmark

About Fr. John Zuhlsdorf

Fr. Z is the guy who runs this blog. o{]:¬)
This entry was posted in SESSIUNCULA. Bookmark the permalink.

29 Responses to There my be a technical problem with the blog

  1. Emilio says:

    Fr, I respectfully suggest you change registrars. The warning message emails from Network Solutions or GoDaddy are pretty annoying, but they sure beat “This domain has expired” on the expiration day…

  2. Brian Day says:

    At least the comments are working again. Yeah!

  3. Geoffrey says:

    Thank you for the “heads up” Father! I kept checking in all afternoon and was becoming worried! I feared the blog was no more! Good luck with getting everything squared away. Isn’t technology great? ;-)

  4. When things settle down a bit, I will be making some changes so that this doesn’t happen again.

    Oddly, I never lost access either on the computer or on my phone.

  5. You’re getting through to Italy, Father…but I was a tad worried around 10 when I kept getting a travel agent site.

  6. Ed Casey says:

    Father:

    You could still see it because you happened to have caught it just right. The DNS servers in your area hadn’t updated from the root server on the same schedule as the DNS servers in those affected geographical areas. Luckily it was caught before all the servers updated. Just so you know, it will be at least 24hrs until all the correct changes propogate from the root to the edge servers.

    I suppose we can offer up the stress, confusion, etc.

    Best wishes,

    Ed Casey

  7. Michael: If you are getting the blog, after getting that other site, then I think the problem is over, for most of Italy at least.

  8. Ed: The fact is that this little bit of disaster has also reconfirmed something that I sometimes forget, in all the frustrations I have with keeping this blog going:

    People do read, and they care about it when there are problems.

  9. Ed Casey says:

    Father:

    Indeed, we read and care, and are inspired, much more than mere words can convey, and greater than you can know.

    Ed

  10. John Polhamus says:

    Just wanted you to know that I was unable to access you at San Diego State University earlier this afternoon, but am getting you at home about two hours later.

  11. Will says:

    Here in Colorado, it went down at about 1400 MDT, came up again about an hour later, went down for a while, and has been up again since 1630 or so.

  12. Terth says:

    I don’t know about the rest of the eastern seaboard, but Florida is working just fine.

  13. Terth: I wonder if that isn’t the first time in a long time that “technical”, “Florida” and “working just fine” have been written.

  14. Victor says:

    I am from Germany, and while your site wasn’t accessible a few hours ago, all is well again by now. BTW, thanks a lot for your good work which is being appreciated a lot!

  15. Elizabeth V. says:

    Dear Fr. Z,

    A New Mexican checking in! I couldn’t access your blog this afternoon, but I can now.

    I missed you!

    I’m sorry about your troubles. Hopefully you’ll have it resolved soon.

  16. Josiah says:

    I could’nt access it from 4:30 until now, just about 9:00. I got so scared I made a post on my blog about it!

  17. Bede says:

    Tacoma Washington checks in… so far as I know, we never lost you.

  18. Matt Q says:

    Father Z:

    What I’m getting is a generic site with travel, shopping and car links.

    Conspiracy theories would not be out of place, as well as the stupid Devil.

  19. Kelly Clark says:

    It’s working for this Boston lady now. Earlier, I was advised to (a) choose the apartment of my dreams and (b) the former owner of the domain had let it expired.

    Alleluia, the domain is back!

  20. Ann says:

    FEEDS are not working right.

  21. Matt Q: No, this was, at its basis, incompetence.

  22. Jon says:

    Father,

    No problem at all in Lancaster, PA, this evening.

  23. Mr. Bayardo says:

    Father,

    Was able to acces in Texas all afternoon and now. Glad your back.

  24. John F. says:

    St. Louis, Missouri no problem.

  25. Father,

    Glad to see you back, it was a bit discomforting to see some generic ad page instead of your blog. However, your site going down today made me do some checking of my own domain names (I have two) the one I use for my real life job (real estate) expires in two days so I’ll renew that one ASAP. I never got emails about my other domain name and when it expired I had to pay a hefty $90 to restore it, before it got auctioned off. Not pleasant, as I really didn’t need to spend money for not paying attention. I’m glad yours was just a mistake on the part of your old hosting provider and all is well. And yes, you were down in New Mexico earlier, when I wanted to post a link to your online confession post.

  26. Brian Day says:

    What got me was that the main page showed up just fine. It was the comment pages that showed the adds.

  27. MSusa says:

    Hey Father, my wise out Aunt would say…”Remember, it is LENT after all!”

    We have had many things to offer up just this week.

  28. Brian: The comment page showed the ads? Weird!

  29. Brian Day says:

    Fr. Z,

    Yes, it was just on the comment pages. I know that the email I sent you with the screen capture is looooonnnnnnng gone, but if you looked at the address bar, it clearly shows it was on a comment page.