Render forward zones into named.conf on every pod #5
Reference in New Issue
Block a user
Delete Branch "benvin/forward-zones-config"
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?
A resolver's conditional-forward zones must be on all pods (config, not replicated data). They were
rndc addzone'd on the primary only, so queries load-balanced to a secondary missed the forwarding — internal names wouldn't resolve.Changes
type:forwardBindZones into named.conf, inside theirviewRefview (or top-level when no views)No CRD change. Merge + tag v0.1.4; then bump the operator image. Enables the puppet-style resolver (view openforwarder + conditional forward zones).