Plesk 12.x / Linux :: Set Master NS (SOA) Record Properly (BIND Does Not Notify NS In SOA)

How to get plesk (12) to set the SOA record properly on existing domains?

Let me explain the issue first. We use PowerDNS supermaster mode as slave servers. The way this works is we configure PowerDNS so that it sees the plesk server as a so called supermaster.

When a so called supermaster notifies the slave servers on a zone update, if it doesn't exist it just adds the zone and pulls it in. This works very nice and without any scripting required (there's only the issue of removing them, I just have a script that deletes all domains that haven't been able to update in 2 weeks every day from the database).

The only issue here is that BIND does *NOT* ever notify the nameserver listed in the SOA. The nameserver listed in the SOA should be the master (and hence - thus plesk itself) and it being a master it should be where the changes occur and notifying it isn't necessary thus, which is why BIND doesn't do that.

Unfortunately plesk doesn't seem to grasp this concept. It will happily put any nameserver in the SOA record. Have adjusted the template and it seems to work ok for new domains now (not sure how reliably though), but it's a major pain for the existing ones. It's very hard to update them properly.

Reapplying template -> no change to master NS/SOA
Switching mode to slave and back to master -> no change to master NS/SOA
Resetting to default -> no change to master NS/SOA

The only way I've found so far is to delete the records manually, add them again and hope it doesn't change the order (yes it does this a lot, you'll have the correct order listed, click apply and the order just changes. Some times it adds them to the bottom of the list, some times to the top - not confusing at all).

Plesk really should be taught that if it's master, it should be the one in the SOA. Whilst my issue is larger due to the supermaster and slaves not creating the zone (and hence my slave not functioning), it is an issue in any setup because a slave listed as SOA will not be notified and doesn't pick up on the changes right away. Depending on the refresh times it might take quite some time for the slave to pick up the change then, which isn't desirable either as it will leave you with a slave that still returns incorrect records.