We all appreciate own3mall's efforts on getting the masterserver back up. I know first hand the sinking feeling when a service you run goes down unexpectedly. This is why sysadmins can affect the global markets for stresstabs, tums, and maalox :)
Now that it's back up, I'd like to propose a more redundant or distributed strategy. My first blush guess would be to drop a loadbalancer/proxy or two that is outside all networks that the masterserverS sit on - perhaps aws (no charges or donations needed). I also own a commercial hosting facility, so I'd be happy to host another masterserver - gratis. The idea being that if one of them goes down, services stay up. There's more than one way to skin this cat, that's just one idea off the top of my head. There is also the issue of one site for all the dns servers related to mohaa/xnull things and that can be fixed easily as well (we run our own dns cluster that is somewhat underutilized).
I'd rather not get bogged down in a hundred post thread of the different ways to accomplish redundancy, for this thread I'd just like to see if the group wants to head that direction - and I'm offering to help.
Best,
Todesengel