Verify Technitium zone data replication to secondary nodes #71

Open
opened 2026-07-22 18:38:25 +00:00 by mconway · 0 comments
Owner

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

dig k3s-internal.conways.info @10.10.2.151
dig k3s-external.conways.info @10.10.2.151

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.

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 ``` dig k3s-internal.conways.info @10.10.2.151 dig k3s-external.conways.info @10.10.2.151 ``` 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.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
mconway/Homelab#71
No description provided.