one authoritative name server and each domain requires ns1.thisdomain.com

[Jim Peters]

I am looking for a way to run the existing name servers I use as the authoritative name server for all the zones I am authoritative for that I currently have a problem with.

For most domains that I have, it is sufficient to list ns1.example.net and ns2.example.net in each zone and publish those names with the registrars as the host record.

For a few top-level domains that I deal with, the requirements of the TLD require that the name of the name server be a subdomain name of the zone.
What I mean is that for the zone anotherdomain.TLD, I have to create NS records called DNS1.anotherdomain.TLD and DNS2.anotherdomain.TLD.  Then I end up their A and AAAA records for ns1.anotherdomain.TLD and ns2.anotherdomain.TLD.

All of my zones currently live in a view named external.

I'm not having any operational issues with BIND/named.   The problem is with the management software.    When it finds the new name server names, it consumes all zones on these servers again as if NS1.anotherdomain.TLD and NS2.anotherdomain.TLD are their servers.    Other than anotherdomain.TLD, none of them are.

Is there some approach in BIND / named.conf I can get to so that "ns1.anotherdomain.TLD and ns2.anotherdomain.TLD" are only seen as the name servers for zones in TLD?

Maybe a view for zones in TLD ... or possibly a separate view for each zone from TLD that needs this treatment of name servers?

Thanks,

Jim Peters
jpeters at dovetailinternet.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20230504/4fa375c4/attachment.htm>