• 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.

NS records created in wrong order

Ying HaoM

New Pleskian
Hi,

For years, I've had the issue with Plesk that it keeps reversing NS records, resulting in a wrong SOA record and in the NS2 not being notified of updates. There is this, but it's not a permanent fix. I don't know what keeps happening, but when people change DNS records, often times the NS records are reversed.

For me, this has nothing to do with the DNS template, because it happens on existing domains which the template is not applied to after initial creation.

Can't this be fixed in a better way? I would like to actually set the NS field in the SOA record.

Current Plesk: 12.0.18
 
Back
Top