After several days of messing with DNS, CNAMES, domain mapping and jimmy caw-caws, www.ericmsmith.com finally maps to my typepad blog. What that means is you’ll see my domain name instead of the slightly more complicated “glimbit.typepad.com”. No big deal really, more of a practice for me since I’m going to be doing this for other folks soon.
My domain registrar made it interesting. I had to resort to sending an email to support because it just wasn’t working, and after a lot of research on the web, forums, etc, I knew I had my stuff right.
Me: I’m hoping you can give me some peace of mind about my domain. Could you please check to see that the www CNAME is setup correctly to point to “glimbit.typepad.com“? I have been checking for the past day with nslookup and I get (the wrong url.) The browser goes to the (domain host’s) parked page. I appreciate your help!
First Support Rep: I am sorry, customer support is not able to troubleshoot custom DNS configurations. You have access to modify the A records and CNAMES for your domain through Total DNS, however as this is an advanced function
we are not able to assist with setting it up. I apologize for any inconvenience.
Now, this is crazy. Total DNS was one of the products I could choose to write for help about, for Pete’s sake. I was a bit p’eed off.
Me: Your response that Total DNS Control is not supported is disappointing. You should remove Total DNS Control from your list of sub-products if you don’t answer questions about it. My guess is that something on your end is not functioning properly. In lieu of your support, I’m going to try deleting the CNAME entry I added through Total DNS Control. Wait 48 hours. Re-add the CNAME. Wait another 48 hours. Is there anything more you can recommend that I do on my side?
I rewrote that last sentence several times, threatening to drop their service, etc. Not a real threat, since I signed up for a 2 year license on the domain. But in the end, as always, I went the less-nasty route. Then … a light shone in the darkness!
2nd Support Rep (Different than 1st): What we meant is that we do not provide assistance with you creating custom DNS records. If it is not working properly on our end, we will fix the issue … The DNS server is updated every few hours. Once you add the record to Total DNS Control, please allow around 5 hours for the server to return
the result.
This person was actually trying to help and this encouraged me. Now, the “5 hours” thing was new. Everywhere else it said 24-48 hours, which is why I was going to wait between attempting to reconfigure the CNAME. But this one was straight with me, and I appreciated it.
I set up the CNAME properly. I started checking my domain using an nslookup service on a website. No dice, my domain still pointed to the ‘parked’ page at the domain host’s site. FRUSTRATION. After 24 hours, I wrote back.
Me: I’ve been checking in on it, and just now (24 hours later) I saw that the canonical name is still “ericmsmith.com“. It should be “glimbit.typepad.com” right? This raises a red flag with me because it seems like it’s had enough time to switch over. Can you help me out? Thanks again for your helpful response before.
See, I’m trying to be nice here, but this is getting old.
Please let us know if we can help you in any other way.
Learn more about our Shared, Virtual-Dedicated, and Dedicated hosting: Click here
Sincerely,
Amber
GoDaddy.com
Customer Service Representative
We would appreciate it if you would click here and complete our Customer Satisfaction Survey. It only takes a couple of minutes and will help us serve you better in the future!
Customer 12/07/2005 03:03 PM
Amber,
I hope this gets to you because I found your response very helpful. I
re-established the www cname alias and pointed it to “glimbit.typepad.com.”
I did this at about 5:30 or 6 EST (not really sure.) on Tuesday. I\’ve been
checking in on it, and just now (24 hours later) I saw that the canonical
name is still “ericmsmith.com”. It should be “glimbit.typepad.com” right?
Here\’s the response from the nslookup:
DNS server handling your query: PARK13.SECURESERVER.NET
DNS server\’s address:\t64.202.165.117#53
3rd Support Rep (yes, different once again): If you changed this within 24 hours, it will not have finished
propagation. This is why the www. prefix still resolves to our parked
page. You must wait a full 48 hours on this. Please let us know if we can help you in any other way.
Now, if you’re not following all this, basically what’s happened is: NO ONE AT THIS DAMN COMPANY IS SAYING THE SAME THING. 1 hour! 5 hours! 24 hours! 48 hours! And the kicker is … I had it right all along, as you’ll soon see. By this time, I’m really losing my patience. So many nasty things came to my mind when I wrote this, but I played it cool.
Me: My initial thought was to wait 48 hours (see my previous email.) However Amber B. said that I would only need to allow 5 hours for the turn around. Since it has been 24 hours, this tells me that something is wrong. Can you help me resolve this error?
Hilarious:
A Support Rep: The zone file normally
refreshes in that time - I had our leads refresh the file, and it is
now resolving. Our apologies for the confusion.
Well be sure and thank your LEADS for helping me REFRESH the friggin file. Wish they could have just done that in the first place, whatever the heck that means. I actually thought about writing them back to ask what exactly happened, but thought it would be more fun to write this post.
I promise never to rant like this again. *crosses fingers*