Fix cobbler.main.unkin.net CNAME to resolve on k8s DNS #491
Reference in New Issue
Block a user
Delete Branch "benvin/cobbler-cname-fqdn"
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?
The cobbler master exports
cobbler.main.unkin.netas a CNAME whose value is the bare hostname (ausyd1nxvm2098). The legacy puppet DNS master loaded this into a zone file under$ORIGIN main.unkin.net., so BIND completed the bare label toausyd1nxvm2098.main.unkin.net.and it resolved.dns-updaterrenders RFC2136 updates with no$ORIGIN, so the same bare label becomes root-absolute (ausyd1nxvm2098.) and dead-ends in NXDOMAIN — the record exists on the k8s authoritative servers (and via the resolvers at 198.18.200.7) but has no reachable address. This is the same failure already documented and fixed for haproxy inprofiles::haproxy::dns.Changes:
valueto the fully-qualified${facts.networking.fqdn}.(trailing dot) so the target is origin-independent and resolves identically on both the legacy zone-file export and the dns-updater nsupdate path.profiles::haproxy::dnsto prevent reintroducing a bare label.