Add `also_notify` and `update_acl` to mydns table
mydns-ng supports "table extensions" for acls and "also-notifies" which could relieve some issues with bind9. Unfortunately ISPConfig seems to drop the corresponding table and hence the added columns each time an update is performed.
My proposal is, to extend the dns_soa table according to mydns-ng´s manual:
CREATE TABLE dns_soa
(
id
int(10) unsigned NOT NULL auto_increment,
sys_userid
int(11) unsigned NOT NULL,
sys_groupid
int(11) unsigned NOT NULL,
sys_perm_user
varchar(5) NOT NULL,
sys_perm_group
varchar(5) NOT NULL,
sys_perm_other
varchar(5) NOT NULL,
server_id
int(11) NOT NULL default '1',
origin
varchar(255) NOT NULL,
ns
varchar(255) NOT NULL,
mbox
varchar(255) NOT NULL,
serial
int(11) unsigned NOT NULL default '1',
refresh
int(11) unsigned NOT NULL default '28800',
retry
int(11) unsigned NOT NULL default '7200',
expire
int(11) unsigned NOT NULL default '604800',
minimum
int(11) unsigned NOT NULL default '86400',
ttl
int(11) unsigned NOT NULL default '86400',
active
enum('N','Y') NOT NULL,
xfer
varchar(255) NOT NULL,
also_notify
varchar(255) default NULL,
update_acl
varchar(255) default NULL,
PRIMARY KEY (id
),
UNIQUE KEY origin
(origin
),
KEY active
(active
)
) ENGINE=MyISAM AUTO_INCREMENT=8 DEFAULT CHARSET=utf8;
SET character_set_client = @saved_cs_client;
Notice also_notify
and update_acl
.
The corresponding fields in the interface will also have to be added.
update_acl will be necessary for multiserver-enhancements where the secondary dns will not have access to the database or where dns-updates from the secondary may be propagated to the master dns. also_notify will be necessary for setups with hidden dns servers, such as intranet and probably split dns.