Delegating a reverse DNS zone along classful boundaries in Address Manager is a simple process although how you configure it depends on whether you are delegating the zone to an external DNS server or to a DNS server under Address Manager control.
If you are delegating a reverse zone from one Address Manager-controlled
DNS server to another Address Manager-controlled DNS server, perform the
following:
- Assign a deployment role to the delegating DNS server at either the 8-bit network prefix or 16-bit network prefix IPv4 block.
- At the child block or network, assign a second deployment role to the server hosting the delegated zone.
Example—delegating the child 2.1.10.in-addr.arpa zone from the server hosting the parent 1.10.in-addr.arpa. reverse zone:
- Create the 10.1.0.0/16 IP block.
- Assign a deployment role to the parent server at the 10.1.0.0/16 block level.
- Create the 10.1.2.0/24 IP network within the 10.1.0.0/16 block.
- Assign deployment roles to the child server at 10.1.2.0/24 IP network levels.
- Deploy the configuration.
The resulting .db file on the parent server will contain the delegation NS records for the two child reverse zones. In this case, ns1.example.com is delegating to ns2.example.com:
If you are delegating reverse zones to a DNS server that isn't under Address Manager control or isn't in the same Address Manager
configuration:
- The process is similar except that you need to create an external server in Address Manager and then assign the deployment role for the child networks to the external server.