To publish NS and glue records to DNS zones running on a Windows DNS server, you add the deployment role at the zone level.
Address Manager uses DNS deployment roles to determine the zone type and the server that is hosting the zone. Deployment roles are also used to create Name Server (NS) and glue resource records on a DNS server. Address Manager does not display NS or glue records in the user interface.
For example, to create a standard primary zone on a Windows server, you add the Master deployment role at the zone (or parent view) level in Address Manager. During deployment, the NS record (and glue where applicable) is added to the zone. You add deployment roles for forward zones roles at either the zone or view level.
|Address Manager Deployment Role||Windows Zone|
|Master Deployment role||Standard Primary|
|Hidden Master Deployment role||Standard Primary with no NS record published in zone|
|Slave Deployment role||Standard Secondary|
|Stealth Slave Deployment role||Standard Secondary with no NS record published in zone|
|AD-integrated Master Deployment role||Standard Primary stored in Active Directory|
|Forwarding Zone Deployment role||Conditional Forwarding|
|Stub Deployment role||Standard Primary Stub|
|None Deployment role||Clears all data from the server to which it is applied.|
Address Manager imports deployment roles at the zone level during the import process.
Deployment Roles for Forward Zones
Deployment Roles for Reverse Zones
Address Manager does not display in-addr.arpa zones in the user interface. Instead, you set deployment roles at the block, or network levels to deploy reverse space.