Now users can delete their own zone, that's asking for trouble in a dummy environment.

it means that there might be some new permission in permission templates that will allow or deny removal of zone for user

I'm using 2.1.4 version: workaround: if only the superusers "ueberusers" should be allowed to delete zones and all other users should not be allowed to delete domains than this can be done by editing one line in the list_zones.php:

find line (86):

if ( $perm_edit == "all" ( $perm_edit == "own" && $user_is_zone_owner == "1") ) {

and replace it with:

if ( $perm_edit == "all" ) {

I'm using 2.1.4 version: workaround: if only the superusers "ueberusers" should be allowed to delete zones and all other users should not be allowed to delete domains than this can be done by editing one line in the list_zones.php: find line (86):

if ( $perm_edit == "all" ( $perm_edit == "own" && $user_is_zone_owner == "1") ) { and replace it with: if ( $perm_edit == "all" ) {

PS: forgot: and if you've the search feature active for your users, the same line can be found under line 82 of search.php. (to disable the delete domain button if a domain was found via search funtion.

If thinking about global disabling of zone removal then your suggestion is ok, but what if we want to disable zone removal only for some users, that's why I was thinking to add an additional permission (e.g. user_can_remove_zone).