> As for the direct cause: We traced this down to our web-developer accidentally removing all > zones and re-creating them. I have experienced this error through this route several times. Alex.