Setting deployment roles at IP block or Network levels - BlueCat Address Manager - 9.0.0

Address Manager Administration Guide

prodname
BlueCat Address Manager
version_custom
9.0.0

To create reverse zones on a DNS server under Address Manager control, you must add DNS deployment roles at either the IP block or IP network.

Just as forward zones are not created on managed DNS servers until you configure deployment roles at either the view or zone levels, reverse zones are not created until you have set a deployment role at either the IP network or block level.

The following examples illustrate this point. For these examples, assume the following tasks are complete:
  • You have created a configuration with at least one DNS server object.
  • You have created a 192.168.0.0/16 IP block object and a 192.168.103.0/24 IP network object.
  • You have created a view named default and a zone named example.com.
  • The deployment role of primary is set at the view level.
  • The example.com zone is marked as deployable.

Example 1: Setting deployment role at an IP block level

  1. Assign a deployment role of primary at the 192.168.0.0/16 block level. Upon deployment, the 168.192.in-addr.arpa zone is created on the DNS Server.
  2. Create a host record named test in the example.com zone that resolves to 192.168.103.50.
  3. Deploy the configuration.

Result: The PTR record 50.103 is created in the 168.192.in-addr.arpa zone. All PTR records are created with a two octet notation.

Example 2: Setting deployment role at an IP network level

  1. Remove the deployment role at the 192.168.0.0/16 block level.
  2. Assign a deployment role of primary at the 192.168.103 IP network level.
  3. Deploy the configuration. Upon deployment, a 103.168.192.in-addr.arpa zone is created on the DNS Server.

Result: The PTR record, 50 is created in the 103.168.192.in-addr.arpa zone. All PTR records in this zone are written out with a single-octet notation.