Search Engine: Elastic

Article ID: 126560, created on Aug 14, 2015, last review on Aug 14, 2015

  • Applies to:
  • Odin Business Automation Standard 4.5


When customers purchases some resource like additional mail account via CP, DNS records of his domain are also changed. The example below illustrates the issue.

The original zone looked like

            *        CNAME
    MX (10)
    TXT     v=spf1 +a +mx ~all

Then  A 

was changed to  A

After that the customer purchased a mail box to increase the number of his mail accounts via Account > Buy resources in CP. And that made the DNS zone look like

    *        CNAME      A     A     A       A  NS  A  MX (10)  TXT     v=spf1 +a +mx ~all  A      CNAME


Software issue PPPM-133 that was fixed in Plesk 11.0.9.


Upgrade the Plesk node to the latest version.

If upgrade is not an option for you, there is a workaround for Plesk versions earlier that 11.0.9.

  1. In Plesk go Tools & Settings > Event Manager and create two event handlers for root user with the actions:

    Default domain, DNS zone updated        highest (100)   root    /bin/bash /usr/local/psa/tmp/
    Domain DNS zone updated                 highest (100)   root    /bin/bash /usr/local/psa/tmp/
  2. After that create a file /usr/local/psa/tmp/ on the Plesk server and put there the folowing script:

    /bin/date >> /tmp/dns_events.log # information on the event date and time
    /usr/bin/id >> /tmp/dns_events.log # information on the user, on behalf of which the script was executed (to ensure control)
    echo "Update domain ${NEW_DOMAIN_NAME}" >> /tmp/dns_events.log
    /usr/bin/mysql -uadmin -p`cat /etc/psa/.psa.shadow ` psa -e "update dns_zone set syncSoa='skip', syncRecords='skip' where name=\"${NEW_DOMAIN_NAME}\"" >> /tmp/dns_events.log 2>&1

624ca542e40215e6f1d39170d8e7ec75 caea8340e2d186a540518d08602aa065 400e18f6ede9f8be5575a475d2d6b0a6 70a5401e8b9354cd1d64d0346f2c4a3e

Email subscription for changes to this article
Save as PDF