1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice

SOA-record changes to secondary DNS after upgrading to Plesk 12

Discussion in 'Plesk 12.x for Linux' started by Frater, Aug 12, 2014.

  1. Frater

    Frater Regular Pleskian

    Oct 17, 2011
    Likes Received:
    I recently upgraded my Plesk 11.5 server to Plesk 12.
    This server is running DNS for all our customers.
    Regularly I run a script I wrote that checks if my DNS settings are correct.
    It checks if the slave DNS-servers can resolve that domain and their serial info is the same.
    It also gives an alert if the SOA-record doesn't contain itself as the primary server.

    This script parsed through all the records all the time without giving any alerts.
    Ever since I upgraded to Plesk 12 I'm presented with domains that suddenly have the secondary DNS in the SOA-record and not itself.
    I have a new secondary DNS-server and the records that give this error are changed to that new slave DNS and that domain is then correct.

    But after a few days other domains then change their SOA-record to represent the secondary DNS instead of itself.

    I already have an idea why this might be happening. These domains are all .nl (Netherlands) and our toplevel provider don't have a primary or secondary.
    I suspect that Plesk is querying the toplevel provider to give the primary server and change the SOA-record accordingly.
    Our toplevel provider will probably give the first entry or Plesk is interpreting the data given and extracts the NS that it thinks is the primary.
    This is speculation!

    But having configured Plesk as authorative DNS wouldn't it imply already that it is authorative?
    Why would it ever change the SOA-record to a foreign nameserver?