• The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Plesk won't trigger DNS Notify on RR change. Works fine when not using Plesk! [BUG?]

iopsec

New Pleskian
Hello guys/Parallels Support,

when adding/changing a RR in DNS Zone Management in Plesk Panel it seems that no Notify is sent to the Secondary DNS Servers. The record appears locally on the Master but nothing happens on the Secondary.

If the change is made directly in DNS Management and not using Plesk, the record is instantly sent to the Secondary without any issues.

This is the second major issue preventing us from using it in production and going past trial.

Any help is greatly appreciated!
Thanks!
 
After further investigations and packet captures, it all boils down to this:

1. when updating RR in Plesk, it will update the Primary Master DNS records and trigger the notify action. However, in the packets containing the Notify, the primary name server and authority mailbox are set to the hostname and admin respectively instead of taking these from the individual zones for which the update was made. After a bunch of packets with this data set in, the primary name server and authority fields are finally taken correctly from what's defined for that specific zone.
2. from the secondary name servers a query request comes in for an incremental zone update (IXFR)
3. primary NS (where Plesk is installed) sends out a query response to those secondary NS WITHOUT the new record information, only with SOA.

When using DNS Manager to edit the zones and not Plesk, the Notify packets are sent with the correct information from the specific zone in the primary NS. The query response from primary to secondaries CONTAINS the new record created and it's visible on the other NS.

It seems to me that there's a Plesk issue here.

Nobody encountered this problem yet??? No Plesk Team support here?

Thanks!
 
The Notify is triggered and consequently the secondary servers are updated both when using the DNS GUI or the PowerShell cmdlets.

However, I wonder why this is not working when managing the DNS zones from within Plesk. I can see the changes in the primary DNS GUI but the added records are not sent over to the secondary servers, only the SOA. Any clues?

Nobody using this architecture: Plesk - Primary/Master DNS with a bunch of other MSDNS - Secondary/Slave DNS?
 
Back
Top