MIAB DNS propagation to secondaries

Help with Setup/Upgrade
1

I have a setup where PowerDNS runs on different servers as secondaries for domains on MIAB. However, I find that when I use acme.sh to generate / update a Let’s Encrypt certificate, the PowerDNS servers are not updated with the new TXT record within a reasonable time so that the validation check of the Let’s Encrypt servers succeeds. Other DNS’s like 8.8.8.8, 1.1.1.1, 9.9.9.9 and more all take about a minute or a little more to get the new record, but PowerDNS not. If I log into the PowerDNS UI and manually force and update, the record shows.

Question: Is there a some trigger in MIAB that I can set to instruct the secondary to update? I thought the xfr:ipaddress entry would do that, but it seems not.

Thanks!

2

I see PowerDNS has the option to allow or block xfr updates, which were not set, so I have now set them to allow update notifications. It seems the problem is entirely at PowerDNS.

1 Like
3

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.