Symptoms
There are 2 or more PowerDNS nameservers registered in OSA environment, for example:
ns1.provider.tld - IP 10.10.10.10
ns2.provider.tld - IP 10.10.10.20
Zones for those domain names are hosted on the same nameservers. When the DNS records for these domains are retrieved, confusing data like below is shown:
ns1.provider.tld. 299 IN A 10.10.10.10
ns1.provider.tld. 14399 IN A 10.10.10.20
ns2.provider.tld. 199 IN A 10.10.10.20
ns2.provider.tld. 14299 IN A 10.10.10.10
Both nameservers have both IP addresses assigned. But in OA control panel only the correct A records for those domains are present.
If the incorrect records are manually removed from the corresponding PowerDNS databases, they are added back upon the next run of "Update PowerDns server" tasks. In OA main system log the entries that add the records back can be found during the task execution (task ID is 1111111 in the example below):
Apr 1 10:00:00.000 : DBG [task:1111111:1011101 1:14141:aefffb70 PowerDns ]: [ DNSManagement::PowerDns::PgConnection::executeStatement] Statement: INSERT INTO records (domain_id, name, type, content, ttl, prio) VALUES ($1, $2, $3, $4, $5, $6), parameters: 100001 'ns1.provider.tld' 'A' '10.10.10.20' 14400 0
Apr 1 10:00:00.000 : DBG [task:1111111:1011101 1:14141:aefffb70 PowerDns ]: [ DNSManagement::PowerDns::PgConnection::executeStatement] Statement: INSERT INTO records (domain_id, name, type, content, ttl, prio) VALUES ($1, $2, $3, $4, $5, $6), parameters: 100002 'ns2.provider.tld' 'A' '10.10.10.10' 14400 0
Cause
Nameserver names and IP addresses can be mismatched when fetched from the OA database tables upon new record creation.
Resolution
This issue is reported to the OA development team as POA-111089: "NS servers order in dns_zones does not match dns_hostings".
For a workaround please contact Odin technical support.