Symptoms

The task Sync the DNS zone domain.com fails with the error below:

system exception, ID 'IDL:omg.org/CORBA/TRANSACTION_ROLLEDBACK:1.0'
Unknown vendor minor code id (0), minor code = 0, completed = NO

If you check /var/log/poa.log, you will find this error:

INF [1:25107:f5b23b90:33881 1:25055:f1fdeb90 dns]: [txn:932305 task:68960 DNSManagement::dns_impl::createDNSRecord] domain_id 2114, host 'sub.example.com.', data '192.168.0.25', type 'A': request to add DNS resource record when there is already such a record (identifier 83531)
ERR [1:25107:f5b23b90:33881 1:25174:f4402b90 PleskIntegration]: [txn:932305 task:68960 PleskIntegration::Implementation::<unnamed>::updateDnsZone] Skip DNS record A sub.example.com., reason: non-fatal error 2061

Cause

It is not possible to create duplicate records in Plesk Automation. Most likely, this is because the DNS record mentioned in the logs was already created in a DNS zone for another domain.

Resolution

  1. The old task will not complete because it was already created with the wrong parameters; thus, you must cancel it first.

  2. Check DNS records for the domain "example.com" whose zone could not be synchronized, and remove the duplicate records:

    For example, the subdomain "sub.example.com" has its own "A" record in the DNS zone, but most likely, the same record was created for the domain "example.com":

    sub.example.com A 192.168.0.25
    

    This record could not be synced because it already exists in the DNS zone of the subdomain "sub.example.com." To fix the issue, delete the "A" record "sub.example.com" from the "example.com" domain's DNS zone.

  3. The new task will be created and will complete successfully.

In case the suggested resolution does not help, please contact Odin Technical Support.

Internal content

Link on internal Article