Search Engine: Elastic

Article ID: 130987, created on Jun 13, 2017, last review on Jun 13, 2017

  • Applies to:
  • Odin Business Automation Standard 4.5

Symptoms

Plesk Automation (PA) is integrated with OBAS. Several PA-hosted domains are not propagated to OBAS-managed name servers. The following messages are displayed in /var/log/messages log on the name server side:

May 19 14:05:02 ns1 named[15411]: client 83.223.216.130#19925: received notify for zone 'domain.tld'
May 19 14:05:02 ns1 named[15411]: zone domain.tld/IN: Transfer started.
May 19 14:05:02 ns1 named[15411]: transfer of 'domain.tld/IN' from 83.223.216.130#53: connected using 83.223.216.250#46045
May 19 14:05:02 ns1 named[15411]: transfer of 'domain.tld/IN' from 83.223.216.130#53: failed while receiving responses: CNAME and other data
May 19 14:05:02 ns1 named[15411]: transfer of 'domain.tld/IN' from 83.223.216.130#53: Transfer completed: 6 messages, 344 records, 8913 bytes, 0.010 secs (891300 bytes/sec)

Cause

Conflicting DNS records reside within one DNS zone:

ftp.domain.tld.     600     CNAME           domain.tld.
ftp.domain.tld.     600     A               192.168.0.253

It is possible to get such DNS misconfiguration using partly PA and partly OBAS functional: A record can be added using PA means while CNAME record can be added using OBAS means. Such behavior was classified as software issue PBAS-30634 and will be fixed in future OBAS releases.

Please consider watching Odin public sources for information about updates in our products:

Marketing news and important announces

Knowledge base, each product update comes with a corresponding KB article.

Workaround

  1. Delete one of the conflicting records either from OBAS or from PA side.
  2. Manage DNS records only by OBAS or only by PA means.

624ca542e40215e6f1d39170d8e7ec75 caea8340e2d186a540518d08602aa065 400e18f6ede9f8be5575a475d2d6b0a6 70a5401e8b9354cd1d64d0346f2c4a3e

Email subscription for changes to this article
Save as PDF