Server Move (1 comment)
So here's the deal. Eddie was using the staff network in my office. When we're relocated to bigger, better offices this spring (mine has a window), we'll move all of our desktop machines onto a new network that's designed to be unnecessarily hard to use. That's fine for my desktop, but I'd like to be able to get to eddie. To facilitate that ease of connectivity, I requested an IP on a different network that will remain usable through the move.
The plan was to do a slow, well-planned transition from one network to the other. The big hitch in all this is that the cso.uiuc.edu domain is old and crufty, so any new hosts in a network are strongly encouraged to use cites.uiuc.edu. No big deal, since I can take my time and plan things out.
...Except that my request for a new IP spawned a request to take away the old one. Gone were my plans for a well-planned, methodical migration, replaced with an unknown deadline. So eddie moved today.
This wouldn't be a big deal, except that UIUC's network policy prohibits me from pointing ck.cx directly at eddie. Instead, it points people at my home datacenter, where a sophisticated redirect set up forwards them to where I'm pretty sure they'd like to go.
ck.cx is -- and so long as I remember to keep paying for it -- will be the preferred way to get to my web presence for the forseeable future. If CITES gets a new name and they rename the hosts, ck.cx will still work. If I decide I want to work somewhere else, I'll see to it that ck.cx will still work.
Summarily, because of my odd hosting situation, it's best for any bookmarks or links to use http://ck.cx/.