Ok, this is particularly confusing to me now.
Why would you want to put one of those into a datacenter? Datacenters are generally for high bandwidth servers and I don't think you're going to be serving up any super high bandwidth.
Following that, it would be MUCH cheaper to host all those bits at home... not hard, pop open a few ports(I suppose, I have not used a QM.NET), get a static IP from your ISP and point nameservers. (or get a dynamic dns updater, dyndns is pretty easy to use). Your programming buddy didn't suggest that at all?
Also, glitching DNS server? at.... a datacenter? Those problems should have been fixed yesterday if people are not able to visit the sites that the datacenter is hosting.
I'd be especially worried if you have clients that need to access the QM with whatever you're doing. What if the datacenter "glitches" again while a client needs the file? what if the QM locks up and doesn't respond to remote commands? Do you have a remote relay on the power of that QM in case you need to power cycle it?
Craig