Search Engine: Elastic

Article ID: 119606, created on Jan 13, 2014, last review on Jul 14, 2018

  • Applies to:
  • Plesk Automation 11.1
  • Plesk Automation 11.5


  1. DNS service node was removed from Plesk Automation 11.5 (PA) and then attached back with renewed IP address.
  2. Failed tasks Sync the DNS zone or Update named in Top > System > Task Manager > Scheduled Tasks.
  3. Too record about required DNS service node but used different IP addresses in Top > Operations > DNS Manager > Nameservers.


DNS service node was not properly deleted from Plesk Automation.


  1. Login to PA management node via SSH as root. Create backup of table plesk.dns_services in PA PostgreSQL database using article How to create backups of Plesk Automation databases.

  2. Check what backup was created successfully.

  3. Delete the redundant record about affected DNS service node with old IP address:

    [root@pa ~] psql -U plesk -h plesk -c "delete from dns_services where name='NAMESERVER_NAME' and ip_address='OLD_IP_ADDRESS';"

    make sure what options 'NAMESERVER_NAME' and 'OLD_IP_ADDRESS' are set correctly, where:

    • NAMESERVER_NAME - Name of affected DNS service node;
    • OLD_IP_ADDRESS - redundant IP address which is no longer exists on DNS service node.
  4. Log in to DNS service node. Make sure that services pem and named in RUNNING state:

    [root@ns ~]# service named status
    named (pid  650) is running...
    [root@ns ~]# service pem status
    pleskd is running
    [root@ns ~]# netstat -antpu | grep pleskd
    tcp        0      0  *                   LISTEN      31386/pleskd
    tcp        0      0             ESTABLISHED 31386/pleskd
    tcp        0      0             ESTABLISHED 31386/pleskd

Start required services if they are stopped:

    [root@ns ~]# service named start
    Starting named:                                            [  OK  ]
    [root@ns ~]# service pem start
    Starting pleskd:                                           [  OK  ]

4. Rerun the failed tasks in Top > System > Task Manager > Scheduled Tasks.

c1ecc6010feff26cb42d1d14a7881dd6 e0aff7830fa22f92062ee4db78133079 caea8340e2d186a540518d08602aa065 33a70544d00d562bbc5b17762c4ed2b3

Email subscription for changes to this article
Save as PDF