Creating an Internal Root Zone - BlueCat Integrity

Creating an Internal Root Zone - BlueCat Integrity - 9.3.0

Address Manager Administration Guide

Locale

English

Product name

BlueCat Integrity

Version

9.3.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 on the view page displays the fact that you are using Internal Root Servers by displaying the message “Using Internet Roots.”

To create an internal root zone:

From the configuration drop-down menu, select a configuration.
Select the DNS tab. Tabs remember the page you last worked on, so select the tab again to ensure you're on the Configuration information page.
Under DNS Views, click the name of a DNS View.
Click the Details tab.
Under Root Zone, click Use Internal Root Zone.
Under General Options, select the Deployable check box to make the root zone deployable.
Under Change Control, add comments, if required.
Click Add. The root zone is added and the Root Zone page opens.
Click the Deployment Options tab. Under Deployment Options, click New and select a deployment option:
- DNS Raw option—refer to Adding deployment options in DNS raw format.
- 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.
- Start of Authority—refer to Adding Start of Authority records.
Click the Deployment Roles tab. Under Deployment Roles, click 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.