June 6, 2010

Domain redirection pet peeve

I’ve had a pet peeve for a long time when it comes to bootstrapping a new site. I always seem to have to update the web server config on a server to forward somedomain.com to www.somedomain.com for some reason or another. There are a few reasons for needing the redirect. DNS is the big technical one. It also just looks pretty bad to have somedomain.com setup, but not www.somedomain.com (or vise versa). I suspect some hosted app providers are getting wise to this and will fix it, but I haven’t run across it yet.

So, I configured the webserver at 174.143.24.6 to use a HTTP 301 redirect from somedomain.com back to www.somedomain.com. For any domain that resolves to that server. Hopefully someone else will find it helpful. Have fun!

I’ll post more details here about how it’s setup and monitored.

Comments
blog comments powered by Disqus