I discovered today that the new DNS automation creates a dedicated file for each IP prefixes.
While this is fine for most production prefixes (as they are stable), it's more of a hassle for infrastructure prefixes (small ones like v4 /31s etc) as they require a matching change of the include in the DNS repo (during both creation and deletion). Which can cause a deploy to fail.
It's not a blocker but maybe there is a suitable way to address this limitation? For example:
- Use the Netbox containers as zone boundaries
- Use static /24 boundaries for v4