Cluster secondary shows permanent "Notify Failed" on catalog member zones

[kolonelkrazy]

Currently running Technitium 15.4, two-node cluster

192.168.1.4 — Primary / "Self"
192.168.1.6 — Secondary / Connected

The cluster auto-created a catalog zone, cluster-catalog.infra, with a bunch of member zones under it. Replication itself is totally fine both nodes serve the same SOA serial, the secondary shows connected, no data problems at all.The annoyance is on the secondary node, every catalog member zone shows "Notify Failed" and it never clears.here's what I think is happening. The cluster catalog has notify set to the secondary's own IP:

notify: SpecifiedNameServers
notifyNameServers: [192.168.1.6] the secondary

On the primary that's correct primary notifies the secondary, great but that same catalog setting gets inherited by the member zones on the secondary too. So secondary ends up trying to send a NOTIFY to 192.168.1.6… which is itself. It goes nowhere and gets flagged "Notify Failed" forever. The clustering feature generated the catalog's notify/transfer config. And I can't fix it cleanly from the zone options either catalog zones reject the ZoneNameServers notify option (errors with "The Notify option is invalid for Catalog zones"), and any static IP list that's correct for the primary is wrong for the secondary.

Feels like either the node should just skip NOTIFY targets that resolve to itself, or the cluster shouldn't push a "notify the secondary" config onto the secondary. Right now it's harmless, replication works, it's just setting off my monitoring alerts like crazy

Is this expected, or a bug in the cluster catalog notify handling?

[ShreyasZare]

Thanks for the post.

On the primary that's correct primary notifies the secondary, great but that same catalog setting gets inherited by the member zones on the secondary too. So secondary ends up trying to send a NOTIFY to 192.168.1.6… which is itself.

Is this expected, or a bug in the cluster catalog notify handling?

This is something that is not observed or reported. The notify addresses you configure at the cluster catalog zone does not apply to any of the secondary zones on secondary nodes.

I would suggest that you share screenshots of the config you have so that the issue is understood better. Please share screenshot for Administration > Cluster section, the cluster catalog zone's notify options, any one of the secondary zone notify options which shows notify failed along with the corresponding primary zone's notify options. You can share them here or send them over email to support@technitium.com.

Also share the error log entries related to notify failure from both the primary and secondary nodes.