A Raspberry Pi 5 on the MGMT VLAN runs Technitium DNS as the sole resolver for all VLANs. Every DHCP scope points here. Every VLAN has a NAT redirect rule that catches rogue DNS queries on port 53 and hairpins them back to the Pi — you can't escape it.
Split-horizon means internal hostnames like pi.<internal-zone> resolve to RFC1918 addresses internally, while externally they either don't exist or resolve to the public IP. No DNS leakage.
Upstream forwarding goes out over DNS-over-HTTPS to Quad9 and Cloudflare, with concurrent forwarding: Technitium queries two upstreams at once and takes the fastest answer. Technitium handles the encrypted session so clients don't need any special configuration. (When this post was first written the upstream was DNS-over-TLS; it moved to DoH since.)
Chrony for Time#
NTP is security-critical. Log timestamps, certificate validity, Kerberos tokens — they all depend on accurate time. The Pi also runs Chrony as an NTP server. All VLANs are redirected to the Pi via NAT, so pool.ntp.org queries from IoT devices land here instead.