At a minimum, you must apply DNS roles at the view level in order for DNS deployment to occur.
You can also apply them further into the DNS core if desired. For reverse DNS, you must apply DNS deployments to either a block or a network in order to deploy the reverse DNS settings for that object and its sub-objects.
|None||This DNS role is not deployed. Use this option for DNS objects that exist, but should not be deployed.|
|Master||This role deploys details and options consistent with a DNS primary. This role is also used on a DNS/DHCP Server 250 with the appropriate DNS options to create a caching-only DNS server.|
|Hidden Master||This role deploys details and options consistent with a DNS primary. However, no name server records are created for the server, thus hiding it from DNS queries.|
|Slave||This role deploys details and options consistent with a DNS secondary.|
|Stealth Slave||A stealth slave is a DNS secondary server that does not have any name server records pointing to it. This is useful for testing purposes or for having a hot spare stand-by server. However, this is not a commonly used DNS role.|
|Forwarder||This role deploys details and options consistent with a DNS forwarder. You must use both the forwarding policy and forwarding options for this role to function properly.|
|Stub||A stub zone contains only the name server records for a domain. Address Manager generates name server records automatically during deployment, so a zone deployed within a stub role will not contain any user-selected details or options.|
|Recursion||This role creates DNS caching servers. For information on the options associated with this role, refer to Recursive DNS in the Address Manager Administration Guide.|