Applicable to:
- Plesk 12.5 for Linux
- Plesk 12.0 for Linux
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 which will be fixed in future micro-updates.
Resolution
As a workaround:
- Login to Plesk admin panel
- Go to Tools & Settings > DNS Template and remove additional NS records. Only the ns1.<domain> should be kept there
- Login to Plesk via SSH
- Edit SOA record in
/var/named/chroot/var/example.comto point to ns1.example.com:
CONFIG_TEXT: ; *** This file is automatically generated by Plesk ***
$TTL 86400
@ IN SOA ns1.example.com. .nameserver.plesk.com. (
2018062302 ; Serial
10800 ; Refresh
3600 ; Retry
604800 ; Expire
10800 ) ; Minimum
5. Increase the zone serial number value to enforce the zone update propagation to DNS slaves:
CONFIG_TEXT: ; *** This file is automatically generated by Plesk ***
$TTL 86400
@ IN SOA ns1.example.com. .nameserver.plesk.com. (
2018062303 ; Serial
10800 ; Refresh
3600 ; Retry
604800 ; Expire
10800 ) ; Minimum
Comments
2 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.
Please sign in to leave a comment.