Search Engine: Elastic

Article ID: 132057, created on Jan 14, 2018, last review on Jan 14, 2018

  • Applies to:
  • Operations Automation 7.0
  • Operations Automation 6.0


The OA name server hostnames are resolved to public and private IP addresses simultaneously:

# dig +short

There are no corresponding A-records for the private IPs in the zone There are only A-records for the public IP addresses. The name server is running PowerDNS.


The name servers were registered in OA with the names like Later, the zone was added to OA, so it is hosted on the servers ns* In such situation, the zone should have so-called glue records (A-records resolving NS hostnames to their IPs) for proper DNS server functioning. These glue records are usually added manually on the zone creation, however PowerDNS module adds such records automatically, taking IP addresses the NS were registered with (in this example, the backnet IPs).

As a result, the zone running on the PowerDNS contains 2 A-records per NS: one is a manually added one, another is an auto-created with the backnet IP. Such behaviour was acknowleged as a software issue #POA-114360.


Please contact your TechnicalAccount Manager in order to clarify the current status of the software issue.

To workaround the issue, please contact Odin Technical Support.

0871c0b47b3b86ae3b1af4c2942cd0ce caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 5356b422f65bdad1c3e9edca5d74a1ae 1941880841f714e458ae4dc3d9f3062d 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0

Email subscription for changes to this article
Save as PDF