We have two Windows Server 2012 DNS servers (primary and secondary) authoritative for our external DNS zones. Both the servers are connected to our internal network, so to improve resilience of the system we've arranged several secondary DNS servers outside our network to store our zones. Those servers run unknown non-MS software (BIND-compatible, I believe).
We cannot make those servers to download our zones. If a name server is specified for a zone, MS DNS server adds glue record for that server to the zone. It doesn't matter if the zone is a forward or a reverse one, MS server adds the glue record nonetheless. However, the DNS servers outside our network refuse to download zones with A records belonging to other domains. They suppose our zones simply contain errors.
The records created in the corresponding DNS file looks like
@ NS FQDN.
FQDN. A IP_ADDRESS
I cannot add a name server record for a zone without allowing the DNS server to create a corresponding glue record, and the external servers refuse to download zones which contain wrong records. I can delete those glue records manually, but the server could recreate them any time I modify the DNS server list for the zone.
The main question: is it possible to prevent MS DNS server from creating glue records in zones when adding secondary DNS serer records?
The additional question: is there any RFC or other official documents which allow or forbid glue records from other domains to be added to a zone file? In other words, is the behavior described above RFC-compliant?