empty-zones-enable should consider zone type 'static-stub' as an existing zone when checking which ones to create
The ARM explains when and why, with empty-zones-enable yes;
, named doesn't create an empty zone because the zone is in use locally already:
The server attempts to determine if a built-in zone already exists
or is active (covered by a forward-only forwarding declaration) and
does not create an empty zone if either is true.
I don't think the definition of "already exists" is wide enough. I assume it includes zone types primary
and secondary
, but I would assert that it should also include static-stub
because if you've added this zone type to your named.conf, you're explicitly saying "this zone exists and I want you to resolve queries for it over here ...".
At the same time, maybe we should also look at other zone types and decide if they also count as "already exists", such as mirror
, stub
, and, for completeness hint
(because, you never know what whacky use case might one day arise?)
But mostly, stub
(if this doesn't already count as "already exists") and static-stub
.