cluster: multiple IPs (gateway + master node) for catalog

[audricd]

hello,

in the following set up:

master node at 10.10.10.2
secondary node 192.168.236.102

they talk through a gateway at 192.136.236.100

UNLESS i specify in the secondary node that the IP to both the gateway IP and the master node as such:

I will get this error message:

on dns-01:

[2026-03-22 19:42:27 UTC] DNS Server failed to notify name server '192.168.236.102' (RCODE=Refused) for zone: 10.10.10.in-addr.arpa
[2026-03-22 19:42:27 UTC] DNS Server failed to notify name server '192.168.236.102' (RCODE=Refused) for zone: lab

on dns-02

[2026-03-22 19:42:27 UTC] [192.168.236.100:33451] [UDP] DNS Server refused a NOTIFY request since the request IP address was not recognized by the secondary zone: 10.10.10.in-addr.arpa
[2026-03-22 19:42:27 UTC] [192.168.236.100:44625] [UDP] DNS Server refused a NOTIFY request since the request IP address was not recognized by the secondary zone: lab

i would be okay with this workaround if it wasnt... because every day, it resets. without any interaction of any kind: the gateway IP removes itself as a source IP for the catalog secondary zone synch. and therefore it gets refused like on the error message above.

how can i force this workaround to stick?
or better yet, is there a cleaner / proper way to do this?

im not sure if this is related buuut... my catalog says my hostname is "invalid". that cant be right?

but the hostname on the nodes are correctly set:

[ShreyasZare]

Thanks for the post. It looks like the gateway in between is doing NAT and thus the IP address is getting translated to gateway's IP address causing the secondary node to reject NOTIFY requests.

The workaround you tried would work normally but since these zones are managed by the Clustering feature, it makes sure the settings are as per the cluster setup.

You can still get it to work by configuring the Notify Allowed Networks option in Settings > General section. This option applies to all zones and will fix the issue you see.

The invalid hostname in the Catalog zone is as per standards recommended by the RFC.

[audricd]

its working!
the 192.168.236.100 got removed recently as expected. but since i added it on the settings as per your instructions, the notification doesnt fail!

thank you very much!

[ShreyasZare]

You're welcome!

[audricd]

#1797 (comment)

solved!