Search Engine: Elastic

Article ID: 130574, created on Apr 4, 2017, last review on Aug 2, 2017

  • Applies to:
  • Operations Automation 7.0

Symptoms

There are several name servers in OSA infrastructure. All name servers are registered as master servers.

Checking SOA record serials for the same zone on different name servers, they do not match:

[root@osscore ~]# dig +short SOA example.com @ns1.provider.com
ns2.provider.com. root.email.com. 1490429141 14400 7200 2419200 300
[root@osscore ~]# dig +short SOA example.com @ns2.provider.com
ns2.provider.com. root.email.com. 1489156387 14400 7200 2419200 300

Cause

The behavior is recognized as a product issue POA-109561: SOA serial differs in master DNS servers for domain

The issue affects only OA 7.0. In contrast with OA 6.0, the DNS serials are no longer stored on OA database side, but generated automatically by DNS update tasks. The tasks can become non-synchronous under high load of DNS changes, and the serials will become mismatched.

Resolution

Workaround for PowerDNS: Add any additional DNS record to the affected zone, process the DNS update tasks and remove the record. This way the zones will get in sync.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 0871c0b47b3b86ae3b1af4c2942cd0ce 1941880841f714e458ae4dc3d9f3062d

Email subscription for changes to this article
Save as PDF