3.1.15 upgrade changes db usernames and permisssions for slave servers in master db
We are using a master/slave setup for dns servers, in which root@Ipv4 and email@example.com need to be users in the master db and they need to have all privileges. After updating the master server to 3.1.15, these slave entries were changed (we couldn't do the update on the slave because of this) - their usernames were changed to ispcsrv2 and ispcsrv3 (we have 2 slave dns servers), and their permissions were reduced - they no longer had all privileges. Is this a newly implemented security measure?
We completed the slave server upgrades to 3.1.15 by re-adding the root@IPv4 and firstname.lastname@example.org and the same for server3, which worked.
My question is whether or not this was the correct way to proceed?
Should we instead be using the renamed usernames for the slave users "ispcsrv2" and "ispcsrv3" when we update the slave servers to 3.1.15 and temprarily giving these renamed users all privileges just for the slave updates? If so, will the all privileges permissions be automatically reduced later (when?) and if so, will dns propagation be affected?
Also, is dns propagation to the slaves going to be affected by this (either way)?
Thanks for letting us know which way to proceed so that dns propagation from the master to the slave is not interrupted. Will this be required from now on for all ISPConfig updates (changing permissions and usernames in the db?)?