records: add domain/IP-range allow+deny filtering #3
Reference in New Issue
Block a user
Delete Branch "benvin/record-filters"
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?
Adds allow/deny filtering so k8s and internal addresses stay out of the authoritative zones.
Why
Hosts publish records the authoritative server should not hold —
*-flannel.1 A 10.42.x(pod CIDR),*-kube-lb0 A 198.18.200.x(LB VIP range),*-nomad A 172.26.x, plus the matching reverse PTRs (200.18.198,2.42.10, …). The daemon currently WARNsNOTAUTH/bad authenticationon those zones. Filtering drops them at the source.What
records.Filter: allow/deny CIDRs + allow/deny domain suffixes, applied to the desired set before reconcile.-deny-ranges/-allow-ranges/-deny-domains/-allow-domains(comma-separated) orDNS_UPDATER_*env.Paired puppet change sets
DNS_UPDATER_DENY_RANGES=198.18.199.0/24,198.18.200.0/24,10.42.0.0/16,10.43.0.0/16.