- Plesk for Linux
- Plesk for Windows
The first NS server that is specified in Tools & Settings > DNS Template > ns1.<domain> is not a primary name server in SOA record.
Changing of any NS record in DNS Template and then applying changes to the existing domains leads to changing primary name server in a domain's zone file.
This is Plesk bug with ID #PPPM-2226.
The issue has been fixed in Plesk Obsidian, consider upgrading to the latest version to be able to select NS server in SOA.
As a workaround:
Login to Plesk admin panel.
Go to Tools & Settings > DNS Template and click on <domain> for NS record ns2.<domain>:
Click OK without modifications:
Then, apply the changes to all hosted domains:
Select Apply the changes to all zones option > OK:
Now verify that such changes are done by logging into the server over SSH.
And checking the named zone files:
# egrep SOA /var/named/chroot/var/example.com
@ IN SOA ns1.example.com. info.plesk.domain.tld. (
- Once the changes are verified, it may take from 24 to 48 hours to propagate the change over the internet.