Files
puppet-prod/site/profiles/manifests
unkinben 918c4f20e1 haproxy::dns: fully-qualify halb CNAME targets (#489)
## Why

The halb publishes service CNAMEs (`git.unkin.net`, `dashboard.ceph.unkin.net`, and every other halb-fronted name) with a **bare target label**, e.g.:
```
git.unkin.net.  300  IN  CNAME  au-syd1-prod-halb-vrrp.
```
`dns-updater` builds the RR with `dns.NewRR` and **no $ORIGIN**, so a bare value becomes root-absolute (`au-syd1-prod-halb-vrrp.`) and dead-ends in NXDOMAIN. Once the k8s bind became authoritative for these zones, that broke resolution of every halb-fronted service (git, the Ceph dashboard, ...). `au-syd1-prod-halb-vrrp.unkin.net` / `.main.unkin.net` resolve fine (198.18.19.17) — only the CNAME target was truncated.

## Change (`site/profiles/manifests/haproxy/dns.pp`)

Emit **fully-qualified** CNAME targets (trailing dot), the FQDN form `dns-updater` expects (per its own test fixture `au-syd1-prod-halb.main.unkin.net.`):
- vrrp cnames: `${location_environment}-halb-vrrp.${domain}.`
- non-vrrp cnames: `${location_environment}-halb.${domain}.`

The matching A records are already published in `main.unkin.net`/`unkin.net` just above, so the targets resolve to the VIP.

---------

Co-authored-by: benvin <neotheo@gmail.com>
Reviewed-on: #489
Co-authored-by: Ben Vincent <ben@unkin.net>
Co-committed-by: Ben Vincent <ben@unkin.net>
2026-07-19 01:37:06 +10:00
..
2024-04-13 22:34:28 +10:00
2025-07-06 11:27:35 +10:00
2023-11-17 22:17:24 +11:00
2025-06-29 13:36:16 +10:00
2026-01-03 21:51:47 +11:00
2024-06-01 22:51:42 +10:00
2024-07-01 22:54:22 +10:00
2025-06-15 17:43:19 +10:00
2024-03-16 16:43:12 +11:00
2024-07-08 22:33:11 +10:00
2026-03-16 23:53:52 +11:00
2023-11-17 22:25:43 +11:00
2024-08-06 22:33:32 +10:00
2025-04-24 16:51:31 +10:00
2025-04-24 23:03:01 +10:00
2024-07-28 01:51:41 +10:00