Secondary NS server is used as primary one in SOA record

Follow

Comments

2 comments

  • 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

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

Please sign in to leave a comment.

Have more questions? Submit a request