• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • 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.

Issue TTL and SOA settings via Azure DNS Extension

FabianN

New Pleskian
The Extension does not Sync the SOA and the TTL for the the DNS entries as configured in Plesk. And by the way, the Plesk server him self needs to be added with in Azure DNS to be resolvable as Name server over Azure DNS as well.
This could be a problem, if you migrate between Plesk servers and the Azure DNS Server are the Primary, and you keep wondering why the name resolution did not work as expected. Recreate the zone is a bad idea, the TTL for the NS records in Azure is 2 days by default and it is not synced with the Plesk Server :(

Another issue I have seen, if you synchronize Zone Aliases, they may be assigned to other Azure DNS Server as the original zone.
 
Back
Top