Articles in this section

See more

Secondary NS server is used as primary one in SOA record

Avatar
Francisco Garcia
Updated
Follow

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 which will be fixed in future micro-updates.

Resolution

As a workaround:

  1. Login to Plesk admin panel.

  2. Go to Tools & Settings > DNS Template and click on <domain> for NS record ns2.<domain>:

  3. Click OK without modifications:

  4. Then, apply the changes to all hosted domains:

  5. Select Apply the changes to all zones option > OK:

  6. Now verify that such changes are done by logging into the server over SSH

  7. And checking the named zone files:

    # egrep SOA /var/named/chroot/var/example.com
    @       IN      SOA     ns1.example.com. info.plesk.domain.tld. (
  8. Once the changes are verified, it may take from 24 to 48 hours to propagate the change over the internet.

Comments

4 comments

Sort by Date Votes
  • Avatar
    Christian Toller

    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

    0
    Permalink
  • Avatar
    Alexander Tsmokalyuk

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

    0
    Permalink
  • Avatar
    pm

    Hi,

    any news on this issue? 

     

    Regards,

    Peter

    0
    Permalink
  • Avatar
    Nikita Nikushkin

    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

    0
    Permalink

Please sign in to leave a comment.

Have more questions? Submit a request

Related articles