Windows DNS Deployment Roles - BlueCat Address Manager - 9.0.0

Address Manager Administration Guide
prodname
BlueCat Address Manager
version_custom
9.0.0

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 primary 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.

You can create eight types of deployment roles in Address Manager.
Address Manager Deployment Role Windows Zone
Primary Deployment role Standard Primary
Hidden Primary Deployment role Standard Primary with no NS record published in zone
Secondary Deployment role Standard Secondary
Stealth Secondary Deployment role Standard Secondary with no NS record published in zone
AD-integrated Primary 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.
Note: Address Manager does not support stub zones or conditional forwarding stored in Active Directory. These zone types are not imported, and they are not affected during deployment.

Address Manager imports deployment roles at the zone level during the import process.

Deployment Roles for Forward Zones

When you assign deployment roles at the view level in Address Manager they are inherited by all child zones (unless overridden by a different role at the zone level). Similarly, if you assign a deployment role at the zone level, any sub-zones inherit it. For example, if you assigned the AD-integrated primary deployment role to a zone named example.com and a child zone named subzone.example.com also existed in Address Manager, the child zone would inherit the AD-integrated primary deployment role. On the next deployment, both zones would be created on Windows.
Note: While it is possible to assign a deployment role for the same DNS server to zones in two or more different views, only the view associated with the Managed server will be deployed. If you have enabled the Data Checker, the following warning will be displayed: Conflicting DNS Deployment Roles on Managed Windows server.

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.