Workaround:

I discover a way to do this configuration using the ***** DNS Manager to notify all servers in the cluster. But is very easy to implement this in a further update of ***** DNS Manager. This will be solve these two situations related:
https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/9045103-plesk-dns-clustering
https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/37996243-multi-master-dns-scheme

Anyway, you can use this to others customers as a workaround for now. Have a lot of posts in forums asking for this.

Let's go to 'gambiarra':
- First, install ***** DNS Manager in both Plesk servers.
- In /etc/named.conf put the same secret key in both servers:

key "rndc-key" {
algorithm hmac-md5;
secret "[KEYHERE]";
};

- In options, add allow-new-zones and allow-transfer like below (changing [IPSLAVE] to you IP Address):

options {
allow-new-zones yes;
...
allow-transfer { [IPSLAVE]; 127.0.0.1; };
};

- Change the lines:
controls {
inet 127.0.0.1 port 953
allow { 127.0.0.1; } keys { "rndc-key"; };
};

- To:

controls {
inet * port 953
allow { [IPSLAVE]; 127.0.0.1; } keys { "rndc-key"; };
};

- Exactly the same configurations have to be done in both servers, just changing [IPSLAVE] to the another one and vice-versa;

-After these configurations, go to ***** DNS Manager and add the other Plesk server. Important: when the ***** DNS Manager suggest the configuration, change the field secret key to the same key used in the /etc/named.conf or don't will works.

- Go to Tools ans Settings > DNS Zone templates > SOA registries templates and select the own server in the Main name server. For example, if you are in the dns1.example.com, select dns1.example.com. After that, go to dns2.example.com and do the same thing selecting dns2.example.com.

- Apply this configuration to all DNS zones and it's done: when you create a domain in one server, the domain zone will bem automatically created in the other, if you change, the update will bem sent, if you delete, the domain zone will bem removed in both DNS servers.

- In my case, I'm using another server (server c) without Plesk to be the third DNS server. It's works too, the configuration is the same, the only diference (but optional) is to put a notify no; inside options named configuration. This will stop the server c to send notify to another servers because it will not host any websites. The server C should be added in the both ***** DNS Manager too, using the same secret key;

The only preoccupation about that solution is to change /etc/named.conf in lines that Plesk could be reset. Anyway, changing the /etc/named.conf and trying to reload and restart named from Plesk and command line no changes the named.conf. I test too obviously creating a new domain, and the named.conf do not replaced too. But the alert of the possibility exists in named.conf.

So if the ***** DNS Manager do these configurations automatically in the next update, will be solve this preoccupation.

Hello,

Have another feature suggestion about this here: https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/37996243-multi-master-dns-scheme

Please vote there too.

Plesk Admins: if it's possible, please unify the two features to not divide votes.

I do not understand why Plesk DNS clustering in Plesk has not been possible for a long time, especially since it is already standard. Many of those who program a reasonable CP integrate these solutions for a long time, especially since I believe that this multi-server function is standard for Plesk and not a paid addon. All functions that contribute to the security of a server should also be integrated at Plesk for free. Or does the group ever need tired cent? then I donate the group geren a few euros !!!!

Indeed there is a link to configure the ***** DNS manager extension, but that implies manually installing Bind at a new server.

Another control panel has a specific free license that allows a simplified installation of it to only host and manage DNS zones. This simplifies installing a DNS cluster on multiple servers.

I believe the idea would be to have a Plesk dnsonly license, where we could install versions of Plesk that would only work as a DNS server, work out of the box with the Salve DNS extension and be able to keep the server updated and secure.

No that is not at all the solution. We use DNS slaves already. The original poster and the other who has commented asks for cluster support like cPanel has implemented it. It seems that you do not want to understand that. Using just slaves does not really work if one want to use several plesk servers.

The user Ender commented earlier :
"Main idea here is domains in DNS cluster that already created in other servers shouldn't be created in Plesk environment. "

Hi, the original poster most likely meant the solution described in here
https://ext.plesk.com/packages/f58eac32-6fda-4886-8d44-d3cb7b98933e-slave-dns-manager

Let us know if it is not what you were looking for

I can't believe you have added all kind of features to Plesk 17 but not basic essential features as DNS clustering. Cpanel has done this quite right. In addition to cPanel features a server should only be able to update it's own domains. Not all domains in cluster. This allows us to offer Plesk VPS servers to our clients that can connect to our DNS cluster.

DNS cluster might be done with 3rd party apps or plesk extensions.
Main idea here is domains in DNS cluster that already created in other servers shouldn't be created in Plesk environment.
If you can provide solution for that then it works seamlessly and people can merge all plesk servers in single DNS server without any problem.

yes, is about make server dns clustering like cPanel does.
In the actually I have a lot cPanel servers, 4 for DNS (master), and the other just connected to them, every change is maded to the master server directly.

I was looking the same functionality between plesk servers, but it doesn't have it.

will be awesome with the all plesk family; between Windows <-> Linux