Symptoms
If the DNS zones are being transferred but are not being loaded then there is likely an error causing the DNS zone to be loaded on the DNS Cluster server and is typically due to an error with named.conf.
Description
When a DNS zone is not loading one of the first things you want to do si check of the function of loading or relaoiding an updated zone works with
rndc reload
While troubleshooting this on a server with named/bind the following was shown.
[14:48:58 dns1 root~]cPs# rndc reload
rndc: 'reload' failed: failure
[14:49:06 dns1 root~]cPs#
On a PowerDNS server the reload command would be:
pdns_control reload
When DNS zones are unable to be loaded or reloaded use the following on either a PowerDNS or named/bind DNS server to see if there are errors.
named-checkconf -z /etc/named.conf
The output may show duplicate DNS zones. When duplicate DNS zones are shown use the following WorkAround to rebuild /etc/named.conf and restart the DNS service.
Workaround
This is what would be used to rebuild named.conf and restart the DNS service:
mv /etc/named.conf /etc/named.conf.orig
/scripts/rebuilddnsconfig