Verify Technitium zone data replication to secondary nodes #71
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
After patching missing Pi-hole-derived records into the conways.info Primary zone on the Technitium primary, confirm the same records actually replicated to the secondary pool via Technitium's clustering.
Check
Compare against the primary (
@10.10.2.150) and confirm they agree. Spot-check a couple of the other newly-seeded records (physical hosts, sso.conways.info) too.Context: this matters because clients hitting the secondary LB IP (10.10.2.151) get answers from whichever secondary pod picks up the query - if zone data hasn't replicated, those clients would still see the same NXDOMAIN failures we just fixed on the primary.