Creating an internal root zone - BlueCat Integrity

Creating an internal root zone - BlueCat Integrity - 26.1.0

Address Manager Administration Guide

ft:locale

en-US

Product name

BlueCat Integrity

Version

26.1.0

An internal root zone is generally used when an organization requires an internal DNS name space to support a very large intranet. The root zone delegates domains to top-level and lower level domains.

Root zones are always created at the view level. This way, you can create a configuration that has a root zone in the internal view, and an external view that uses the Internet root servers.

When you are using internal root servers, the Root zone section in the expanded details section for the view displays the internal root server being used.

To create an internal root zone for a view:

Select the DNS tab in the sidebar, then select Views.
Select the row containing the DNS view in the Views table, then select Use internal root zone in the expanded details section.
Under General, select the Allow this zone to be deployable checkbox to make the root zone deployable.
In the Change control section, add comments if required.
Select Create.
The root zone is added and the Deployment options tab in the Root zone page opens.
Select New, then select a deployment option from the drop-down menu:
- DNS option—refer to DNS deployment options. A root zone can have two deployment options associated with it, Allow Zone Transfer and Allow Query. These roles can be set at the root zone level or they can be inherited from the view.
- DNS raw option—refer to Adding deployment options in DNS raw format.
- Start of authority—refer to Adding Start of Authority records.
After you create a deployment option, select the Deployment roles tab, then select New. You can set the DNS deployment role of Primary to the root zone. For more information, refer to DNS deployment roles.

A root zone can only be assigned the primary deployment role. If a deployment role isn't explicitly set, the root zone inherits the primary deployment role set at the configuration level. If a deployment role isn't defined, the root zone isn't deployed.