Okay, I just realized that bit.ly offers free custom domain shortening. Amazing. I really wonder how they are generating cash out of their service. I would have thought this would be a paid service like custom domains are for wordpress.com.
It was quite easy to setup. I first headed over to www.dot.tk to grab a free domain (yes, I’m cheap). Unfortunately bart.tk was already taken so I took barts.tk. All I had to do was set the A record for barts.tk to 220.127.116.11 and then go over to bit.ly and add barts.tk as custom short domain. Finding this setting is a little buried, I had to go to settings and then advanced as opposed to finding it as an option under one of the main tabs like profile.
I’m curious now to see what kind of stats I will get out of my domain shortener now.
Well, this evening I decided to fork over the $13 to have a custom domain setup for my wordpress.com blog so you can get here by going to bartsipes.com instead of bartsipes.wordpress.com. Overall it was a pretty painless process. From the Dashboard I just went to the Store and selectde “Mapping.”
From there I marked that I already own a domain and entered bartsipes.com. I then paid for it with my PayPal account and was taken to the following screen.
At this point I just hoped over to 1and1.com where I have my domain registered and changed my domain’s name servers to NS1.WORDPRESS.COM and NS2.WORDPRESS.COM. (Full instructions available at 1and1 support)
After this a funny thing happened when I went to bartsipes.com. Chrome wouldn’t render my site because of a redirect loop. It took a minute for that to make sense. I had my domain at 1and1.com setup to do a HTTP redirect to bartsipes.wordpress.com (the cheap way to do a CNAME ). Because I had just switched bartsipes.com in the above configuration to be the primary domain, wordpress.com was redirecting bartsipes.wordpress.com to bartsipes.com where 1and1 redirected me to bartsipes.wordpress.com. Ah…the beauty of redirects…
So, I’ll be leaving bartsipes.wordpress.com as the primary until my name server change is propagated through the interwebs.