And so we come to the end of National Blog Post Month (NaBloPoMo). Now I was planning to try to sum things up, but that will have to wait one more day, as a friend and I need some help from the blogosphere.
This story begins last spring, when a good friend got accepted to law school. Among other ambitious ideas, Boone ran an online support and critique group for Milwaukee area writers. I built a WordPress site for this project, but now that he was leaving Milwaukee temporarily to hit the books, the workshop would have to run itself for a while.
The writers were notified of the situation, and Boone went off to law school. Apparently, we all forgot about the website. Last night, Boone had some downtime, and was thinking about updating the WordPress site, and making plans for its eventual revival. Except he couldn’t log in to WordPress, nor would WordPress reset his password. Boone (who is not a technical person) emailed me about this dilemma. I went to the site–and I couldn’t log in to WordPress either. The interesting thing is that the site itself (at least the home page) displayed normally.
Both of us could get into the hosting account, but when I tried to look into the site’s database admin tool, I got a Server Not Found message. Couldn’t access the database online. After Boone had a chat with his host’s tech support, and just before I started researching their proposed solution, Boone wrote to tell me the domain had expired on July 1, and apparently had been scooped up by someone in the interim. That would explain much.
A WhoIs search for the owner told us the domain had been registered with GoDaddy in August, and the Nameserver was at domaincontrol.com in Arizona. Incidentally, GoDaddy was not the original host for this site. We later learned that domaincontrol.com is a GoDaddy subsidiary, but I’m no longer sure that’s relevant. You see, I’ve never fought with hosting companies, or had a domain I controlled expire, so this is new to me.
Good news is that Boone got a new domain for his site, and we still have the old database backed up. So I think we’ll be ready to go when it’s time to relaunch.
Less happily, Boone is concerned that the new owner/squatter is still using his (and his writing collaborators) content, presumably until whatever replacement content arrives. Boone would like to see that content disappear (and as long as we’re wishing, get a redirect to the new site).
To those of you out there with more experience in these situations, how does one find and contact the new domain holder? We’re assuming that large sums of cash would be required to reclaim the domain, but where do you send the cease-and-desist with regard to the content? Any other tips and ideas?
Thanks to all for any help you can offer!
Tomorrow, some more lessons learned during NaBloPoMo. A bunch of folks have done this already. Listed below are some of them.
- Last day of NaBloPoMo (geekoutsw.wordpress.com)
- NaBloPoMo, Over and Out (notapunkrocker.wordpress.com)
- Nearly 30 Days of Blogging – My Semi-Successful Journey Through NaBloPoMo ’13 (javaj240.wordpress.com)
- NaBloPoMo: Auf Wiedersehen, Adieu (babywithatwist.wordpress.com)
- The last day of NaBloPoMo (missbenoist.wordpress.com)
- I Did It !!! ……… ( Day 30 … The final day of NaBloPoMo ) (rosiewrites2.wordpress.com)
- NaBloPoMo: 30 Days of Blogging About my Ordinary Life (lifewellblended.com)
- November NaBloPoMo: I Did It! (imnotthenanny.com)