Article ID: 130562, created on Apr 3, 2017, last review on Apr 7, 2017

  • Applies to:
  • Operations Automation

Symptoms

named service does not start and throws the errors like:

zone a.b.provider.com/IN: NS 'ns1.a.provider.com' has no address records (A or AAAA)

Update named tasks may fail with the same output.

The OA managed DNS server has the name of ns1.a.provider.com (fourth-level domain name).

OA also hosts the DNS zone for 'provider.com' domain (second-level domain name).

BIND package version has been updated recently on the DNS server to version >9.7. This happens automatically on OA upgrade from 6.0 to 7.0.

Cause

Starting from version 9.7, BIND has a more strict check for NS records in DNS zones, so if the NS entry points to a subdomain and A record is not defined for it in the zone, the zone validation does not pass. BIND requires glue records to be added for the NS records.

The OSA behavior will be improved in scope of POA-110901.

Resolution

Edit the zone file and add these lines:

a.provider.com.    IN      NS      ns1.a.provider.com.
ns1.a.provider.com.        IN      A 203.0.113.2

Search Words

has no address records (A or AAAA)

DNS name servers not in sync

has no address records (A or AAAA)

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF