Search Engine: Elastic

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

  • Applies to:
  • Odin Business Automation Standard 4.5

Symptoms

DNS records are not propagated to OBAS-managed name servers. The following messages are found in /var/log/messages on OBAS side:

May 24 14:35:40 billing pdns[25649]: binding UDP socket to '0.0.0.0:53': Address already in use
May 24 14:35:40 billing pdns[25649]: Fatal error: Unable to bind to UDP socket
May 24 14:35:41 billing pdns[25373]: Our pdns instance exited with code 1
May 24 14:35:41 billing pdns[25373]: Respawning
May 24 14:35:42 billing pdns[25650]: Guardian is launching an instance
May 24 14:35:42 billing pdns[25650]: Reading random entropy from '/dev/urandom'
May 24 14:35:42 billing pdns[25650]: This is a guarded instance of pdns

"Netstat" utility displays the following output:

# netstat -apn|grep 53
tcp        0      0 127.0.0.1:53                0.0.0.0:*                   LISTEN      28112/pdns_recursor
udp        0      0 127.0.0.1:53                0.0.0.0:*                               28112/pdns_recursor

Cause

Installed pdns-recursor package is taken from a third-party repository:

# rpm -qa | grep  pdns-recursor
pdns-recursor-3.7.3-1.el6.x86_64

While the default package shipped with OBAS looks as follows:

# rpm -qa | grep  pdns-recursor
pdns-recursor-3.7.3-1.x86_64

Third-party package configuration files are located in a different place.

Resolution

Please contact Odin technical support for assistance.

624ca542e40215e6f1d39170d8e7ec75 caea8340e2d186a540518d08602aa065 400e18f6ede9f8be5575a475d2d6b0a6 70a5401e8b9354cd1d64d0346f2c4a3e

Email subscription for changes to this article
Save as PDF