#5139 New DNS zone template issue

[André Fernandes]

After upgrading from 1.820 to 1.881 I've noticed that the zone declaration template has changed.
We're using webmin to manage a master DNS server with 4 slaves.

Adding a "test.com" zone in the master will add this to the named.conf file:

zone "test.com" {
type master;
file "master/test.com.public";
also-notify {
xx.xx.xx.1; # slave addresses
xx.xx.xx.2;
xx.xx.xx.3;
xx.xx.xx.4;
};
allow-transfer {
xx.xx.xx.1; # slave addresses
xx.xx.xx.2;
xx.xx.xx.3;
xx.xx.xx.4;
};
notify yes;
};

We have a global allow-transfer and allow-notify which gets overriden by these settings, which is a problem since the network interface used for webmin master-slave connections is not the same that is used for DNS zone transfers, and breaks the automatic provisioning of zones on the slaves (they will see a "refused" response to zone transfers).

I'm aware that we can remove these via the "edit zone options" section in webmin, but that becomes a hassle.
Is there a way to modify the zone configuration template so as not to include the allow-transfer and also-notify directives? Could this be added as a yes/no option when creating the master zone?

We face a similar issue with the creation of the zone configuration on the slave servers, it adds an "allow-transfer { master-ip-addr; }; " to the zone declaration which is unnecessary:

zone "test.com" {
type slave;
masters {
yy.yy.yy.123;
};
allow-transfer {
yy.yy.yy.123;
};
file "/var/named/slaves/test.com.public";
};