New tld functionality is fragile on invalid domains

In the full integration test there is an invalid domain "co.za". This causes scheduling of a snapshot job to be stopped and the job is deactivated when the domain is read. It is not even possible to browse/edit the domain in NAS. Also the failure results in the entire very long tld regexp being both logged and emailed.

A single bad domain name should not kill a snapshot job, and I would suggest it should not kill any job - especially as deleting a domain from NAS is (by design) not possible, except by hacking the database.