Moving my photoblog to it's own domain

This past weekend I set up a new domain for my photoblog. I changed the name from a subdomain of clintmcmahon.com to Skyway Hours, with the new URL skywayhours.com. I set up a redirect from the old URL to the new URL so that links, RSS feeds and all traffic would automatically flow to the new URL. However, I ended up bricking the original DNS entry during the process, so the redirect was down for the entire weekend.

Both sites run on a single Linux VPS that I maintain, so moving the blog to a new domain only required updating the DNS entry and setting up the web server to serve the new domain.

After updating the DNS, I created a redirect and successfully tested that traffic to photos.clintmcmahon.com would be redirected to skywayhours.com. Requests to photos.clintmcmahon.com served kywayhours.com. Great, I thought, my work here is done.

It wasn't. My brain was in cleanup mode after the move and decided that I didn't need the original subdomain, because I wasn't hosting anything from it any longer. So I deleted the photos subdomain from the clintmcmahon.com DNS entry. Doing that broke the redirect to the new URL.

I found out I broke the redirect on Monday morning. I was just thinking about the change, and something inside me told me to check that the redirect was actually working. Turns out it wasn't. All traffic to photos.clintmcmahon.com was getting a "can't find this site" error message. I checked the server to make sure the site was set up correctly. It was. Next I went to verify that the redirect was functioning, and that's where I realized the photos subdomain was gone. That explains why the redirect wasn't working.

After I re-added the photos DNS record to clintmcmahon.com, the redirect came back up, so any RSS feeds or links now automatically send the request to skywayhours.com, like they should have from the beginning.

This blog doesn't have a comments section. Reply by email - I'd love to hear what you think.