DNS Server failed to notify
Closed this issue · 3 comments
Great product, we recently started using this our datacenter -
I have the following setup -
I have a catalog zone set up in the primary and a corresponding secondary catalog zone in the secondary. I have followed this guide - https://blog.technitium.com/2024/10/how-to-configure-catalog-zones-for.html
Auto zone provisioning is working, but somehow zone notify is not working. I always get this error -
[2024-10-23 07:42:58 UTC] DNS Server failed to notify name server 'x.x.x.x' (RCODE=Refused) for zone: test.com
[2024-10-23 07:42:58 UTC] DNS Server failed to notify name server 'x.x.x.7' (RCODE=Refused) for zone: test.com
[2024-10-23 07:43:04 UTC] DNS Server failed to notify name server 'x.x.x.x' (RCODE=Refused) for zone: catalog.zone
[2024-10-23 07:43:04 UTC] DNS Server failed to notify name server 'x.x.x.y' (RCODE=Refused) for zone: catalog.zone
[2024-10-23 07:43:43 UTC] DNS Server failed to notify name server 'x.x.x.y' (RCODE=Refused) for zone: test.com
Any idea what could be wrong?
Thanks for the compliments and details. The only reason a secondary DNS serve refuses notify (apart from zone not hosted case) is that the source IP address of the notify request does not match with the configured primary name server address. You can check the DNS logs on the secondary DNS server instances and confirm if that's the case.
If your primary DNS server has multiple IP addresses then ensure that you have configure all of them in your Secondary Catalog zone's options, or just ensure that the IP address being used by primary for the notify request is configured. You can check the secondary DNS logs to know which IP address is being used by primary DNS server to send those notify requests.
Let me know if that fixes the issue.
Thanks @ShreyasZare
it was indeed a multiple IP issue, the node has multiple IPs. it was sending traffic from different Ip that were configured for the container
Issue is solved
You're welcome. Good to know that you got it fixed.