Applicable to:
- Plesk for Linux
- Plesk for Windows
Symptoms
-
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.
Cause
This is Plesk bug with ID #PPPM-2226.
Resolution
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.
Comments
12 comments
I use Plesk as primary name server and two other nameservers in SLAVE mode. (Plesk Onyx Version 17.8.11 Update #17)
In this scenario, the fix did not work for me.
First of all, there is no folder /var/named/chroot/, I only have /var/named/run-root/.
So I modified the corresponding file in run-root/...
Modification of that file didn't fix the wrong SOA record, as it doesn't trigger a domain update.
Forcing a domain update by creating a random NS entry causes the change in the "example.com" file to be overwritten with the wrong SOA record again.
I don't want to apply the modified DNS template to the domain, because there are many additional NS records.
Also, using only a single nameserver is not a good idea at all.
Please update this workaround, so that it can safely be used on existing domains without changing/deleting additional NS entries.
Regards,
Christian
www.tethis-it.at
@Christian To enforce the zone update propagation to the slave servers, please increase the zone serial number value when SOA record is fixed. The serial number is in the same config file.
Hi,
any news on this issue?
Regards,
Peter
Peter, the bug is going to be fixed in the next Plesk major version
Subscribe to this article (click the "Follow" button at the top of the article) in order to be notified when the bug will be fixed
27. September 2019, so more than half a year later, this bug is still present in the version Plesk Onyx Version 17.8.11 Update #68
When is a fix expected?
Hi,
This has been fixed in Plesk Obsidian: it is possible now to select what NS server will be in SOA record.
Hi,
Thanks for the fix in Plesk Obsidian !
Can this be done through command line ?
It would be great, to fix this for many domains.
Thank you
@Benoît Oua the provided workaround fixes all domains.
I was referring to the Obsidian GUI setting, where you choose, in the SOA settings of a domain, the primary NS server.
Is there a command line equivalent to this?
Thank you
@Benoît Oua
Since plesk bin server_dns utility which manages the server DNS template only has the 'add' option in regards to NS records, the change can only be done via GUI.
@Leonid Gukhman
As the GUI setting in Obsidian is located on each domain, in the SOA tab, if a command line equivalent exists, wouldn't it be in the plesk bin dns utility ?
(not the server_dns one)
Guess it should be something related to SOA as it is set in the SOA tab.
I can see some new options about SOA in this command help, not yet shown in the documentation though.
But not any option about setting the primary NS server for one domain yet :/
@Benoît Oua
Indeed, choosing Primary Name Server is possible for a domain under SOA settings in DSN Settings in Plesk Obsidian. However, there is no CLI implementation for this option in Plesk yet. Please submit a request for this feature on our UserVoice portal: https://plesk.uservoice.com/forums/184549-feature-suggestions
Please sign in to leave a comment.