One of our server providers, the one that hosts our california location for our Mumble servers (and this blog too, for what that’s worth) is pulling our old IPs (which were a sub allocation from one of their carriers, Cogent) and replacing them with their own direct allocation.
Because most of our Mumble hosting clients access their servers via IP address, rather than a DNS hostname, it’s creating quite a bit of a nightmare. At the moment I’m wrestling with trying to get the glue records changed for ns1.sabrienix.net via Moniker. GoDaddy was easy to change, because their support people already walked me through it once.
Moniker is like pulling teeth, I can’t seem to find the option anywhere, and I tried changing the domain’s nameservers and changing them back… but nothing. It’s like eating a month’s worth of cheerios trying to lowering bad cholesterol only to have the doctor tell you nothing’s improved. Admittedly their support folks haven’t gotten back to me yet, but hopefully we get it figured out sooner rather than later.
Changing the websites over should be a pretty transparent process, I’ll just have Apache listen on both IPs at the same time for each hostname… change the A records over and it shouldn’t affect anyone, then once the TTL expires no one should be using the old IPs.
That’ll just leave the Mumble servers, which I’m trying so hard not to mess up anyone’s day but most people aren’t responding to our mass emails. 