No, that's not what happens. There was unfortunately a misconfiguration with these domains which led to the problem that you saw. In fact, I sent you an email about this problem about 10 minutes ago.
The misconfiguration occured because a user entered a virtual domain address, but no target address. We failed to check for this possibility in our web application. The lack of a target address caused a number of virtual domains to become corrupted for a few hours today. We are currently attempting to contact those people with domains impacted by this problem.
The failure to check for empty targets has actually been in the web app the whole time--it's just that today was the first time that a user entered an address without a target, thus triggering the problem.