Well, I never thought I'd spend a Thanksgiving fretting over domain mapping, CNAMEs, Total DNS Control, domain forwarding and masking, and the like. I never really thought I'd know what any of this means. But it's been a techie adventure week for me in our quest to switch over from our old godaddy hosted blog to the new typepad blog.
So first off, I want to apologize for any difficulties you may have encountered in trying to access our site over this past week. It takes 24-48 hours (on average) to set up the domain mapping from our godaddy (registrar site) to our new typepad blog hosting service. I made a mistake the first time, so we got a partial mapping thing going for a few days. Due to my frustration with that, I messed with godaddy Total DNS Control some more, and chewed my fingernails and worried a lot, and was even plagued with bad dreams over getting this darn thing to work properly. After waiting 48 hours the second time, I finally turned to the power of google to see if there were any other resources out there. Lo and behold, there were several kind bloggers who validated my pain and blogged about their challenges getting domain mapping between godaddy and typepad to work. Thank you Mad About Madrid and Blogging Business for letting me know I wasn't the only blogger in the world struggling to set up domain mapping. Also, for clarifying the difference between domain forwarding (and masking) and mapping.
I realize this post isn't the usual cup of tea you may have come to expect from ReadySetMom.com, but I did feel it was important to give back to the blogging community and share the "gotchas" I encountered, so that others may be spared my pain:
1) When I first went to edit my CNAME in godaddy, I changed the first field from "www" to "www.readysetmom.com" which was not right. The first field should remain untouched as "www". The second field is where I needed to put "readysetmom.typepad.com". I did that, but with the mess-up in the first field, we were getting the domain mapping to work only inconsistently.
2) Then I tried to use godaddy's instructions on domain forwarding, and managed to loop between the forwarding and domain mapping. Not what you want to do at all. Some time on the godaddy helpline got me to stop the domain forwarding and stick to the typepad instructions of domain mapping instead.
3) Last, it took over 48 hours for the domain mapping to finally kick in to my servers. I was near the point of panic then, as our site had loaded only error messages for days on end, and I feared all our loyal readers were going to guess we'd gone belly up. It took about 50 hours. So don't panic (like I did) if you've waited the requisite 24-48 hours and it's still not working. This takes lots of patience to give proper time for the mapping to propagate across the internet.
So that's it. I hope this will help others bloggers on the "domain mapping with godaddy and typepad" road. And for the regular ReadySetMom readers, I promise my next post will be more on topic. Happy Thanksgiving!!