Thank you! :-)

Is there any solution for windows?

It would be really great to have "also notify" in the dns templates to notify specific servers for zone transfers.

something like this....

zone "example.com" {
....
also-notify {10.0.1.2;};
....
};

@Ferry: You can have BIND send NOTIFY's to masters as well:

Add "notify-to-soa yes;" to /etc/named.conf in the options container.

@Douggie if it fails it's probably because either of these:
* Zone transfers are not allowed - you should add the slaves to global ACL so they are allowed to do zone transfers on all domains on the plesk side
or
* BIND is not properly sending notifications. This also happens for example if BIND sees one of the slaves as master (has to do with SOA/order). BIND will *NOT* notify masters - only slaves.

I agree with Tozz.

Simply configure 1 or more PowerDNS servers to have the plesk as supermaster. Edit the DNS zone template to list the PowerDNS slaves.

Bind with send notification on domain creation. PowerDNS will automatically pick it up and replicate.

Leaves you with 1 issue -> removal of domain. This does not happen automatically. If you don't care much, like I, as the DNS server won't be responsible for answering any more either, you can just leave it there for a couple of weeks and run a query on a weekly basis that deletes domains that haven't been able to update in say 4 weeks. Or add a script to plesk that on removal removes it from the database on the PowerDNS side.

Here's a clean-up query for those that care. Include it in a daily cron job or whatever on the PowerDNS server. This will delete all domains in there that haven't been able to update (and are thus removed from the master - unless it's down for a really long time) for 4 weeks.

delete domains, records from domains, records where domains.id = records.domain_id AND domains.last_check < (unix_timestamp() - 2592000);

@Douggie: We are running Plesk 10 up to Plesk 11.5 and all versions in between :-) I haven't had any issues with new zones using PowerDNS supermasters. What issues are you facing?

Regarding removed domains.. We use a little shell script that parses PDNS syslog file and do some checks with 'dig' on domains that give errors according to DPSN logging. If our checks confirm the zone is no longer available on the master, we delete the zone from MySQL (we use mysql backend in PDNS).

We use this script because we also have non-Plesk machines as masters. Plesk has a system to call scripts upon certain actions. This could be used to remove zones, but we are not using that at this moment.

Tozz - Also what version of Plesk are you running?

We did extensive testing with this in PP10 and it worked well, even in the first version of 11. But since 11.5 the replication of NEW zones is less than reliable - existing zones update fine, just new zones that seems to be unreliable. A ticket to support also failed to resolve this as it is largely unsupported using PDNS.

Are you running PP11.5 and using PDNS or a previous version of Plesk? Can you get new zones to replicate correctly to PDNS? And how are you removing zones when a customer is disabled or deletes a domain ?

Interested to know cause I would rather use PDNS instead of Bind as the front end Authoritative servers.

Sergey's extension does all this and works quite well, we have been testing it for about 2 weeks now without any issues. We also don't have to run scripts to remove inactive domains like you do with PDNS' scenario. The only issue i have is that Sergey's extension uses Bind as the Slave DNS where we prefer PDNS like you. But Bind is good and we are about to migrate our prod system to use Segey's extension.

Tozz how do u remove domains using supermasters in pdns? Are you running scripts to clean that up on a regular basis?

I believe this should _not_ be implemented. Have slave support is something that can be configured in 5 minutes.It is just a matter of setting up PowerDNS with Supermasters on your slave server and you are ready to go.

Besides PowerDNS Plesk already has 'hooks' to run scripts on certain actions, so a non-PowerDNS implementation could also be made.

I feel some of these 'feature requests' (like this one) are to compensate for a lack of technical knowledge of the Administrator. IMHO Parallels shouldn't focus on these requests.

This is a must-have solution. The only reason I moved to another rival product is because of ease of DNS-Management

You can try next extension
http://ext.plesk.com/packages/f58eac32-6fda-4886-8d44-d3cb7b98933e-slave-dns-manager

Your feedback will be greatly appreciated.

P.S. http://forum.parallels.com/showthread.php?289458-How-to-configure-two-servers-Plesk-11-5-to-work-as-primary-and-secondary-namservers

Plesk 11.5 has 'Remote DNS' feature. So you could register own script as backend for Plesk DNS service. And your script could implement automate master/slave relations.