Stub zones are similar to forwarding zones because they allow your server to send
recursive queries directly to specific DNS servers. However, whereas a forwarding zone is just an
entry in a configuration file, a stub zone is an actual zone file.
It is named for the fact that it represents a stub of the actual authoritative primary zone
located on a different DNS server. A stub zone contains the authoritative zone’s SOA record, NS
records, and possibly the glue records. The server hosting the stub zone gets these records from
the primary name server holding the authoritative zone. In Address Manager, this zone type is
often used with Other DNS servers (external DNS servers), where the Other DNS server represents
the authoritative primary.
Note: Address Manager does not support Stub Zones stored in Active
Directory, so it cannot import them or deploy them. However, any stub zones stored in Active
Directory are not affected during deployment.
Importing stub zones
When you import a stub zone from a Managed Windows DNS server, the following data is added
during the import process:
- The zone with two deployment roles: a stub role assigned to the Managed Windows server, and
a primary role assigned to the other DNS server (assuming that the primary is not managed from
- An Other DNS server object that represents the external DNS server.
For more information on Other DNS servers, refer to Other DNS Server.