> Almost always you'll want to redirect a bare domain like iskettlemanstillopen.com to www.iskettlemanstillopen.com. Registrars like Namecheap and DNSimple call this a URL Redirect. In Namecheap you would set up a URL Redirect like this:
Coincidentally yesterday I snapped and decided that no longer was I happy using a URL forwarding service that requires configuration or running a web server that redirects old domains, so I built http://cnamer.com/.
That looks like an extremely useful service (good work!), but your examples (source.com.) don't work, since the zone apex can't be a CNAME (this is addressed in the article under "Why CNAME is Messed Up"). So this can be used with www.source.com. but not source.com.
The version live right now is just a proof of concept more than anything, once I've got a few hours spare (hopefully sometime this week) I'm going to rebuild it to operate in a sane manner and will benchmark the load it can support, the Linode itself shouldn't have problems supporting millions of requests a day, it'll be cnamer itself that causes a bottleneck if there is one. Worst case if it turns out there's too much usage for the Linode to support (unlikely...) I'll upgrade the server / move it elsewhere. I was hoping to rebuild + benchmark it before mentioning it anywhere but this blog post seem super relevant heh.
Coincidentally yesterday I snapped and decided that no longer was I happy using a URL forwarding service that requires configuration or running a web server that redirects old domains, so I built http://cnamer.com/.
That will redirect source.com to google.com. That redirects http://cnamer.samryan.co.uk to minotar.net/avatar/citricsquidThe code powering it sucks at the moment and I intend on adding the ability to use TXT records to set the redirect but it /works/ for now.