How to move deployment roles.
The Move Deployment Roles feature is used to move deployment roles from one server to another. For example, you can add two separate Other DNS servers each representing the same external DNS server to Address Manager. One server has a host name only from an import of delegation, and the second server has an IP address from an import of a stub zone.
Since you only need a single Other DNS server representing the external server, you
can delete one of them. However, before you delete it you can use the Move
Deployment Roles feature to move the roles to the other server.
Note: You cannot
move deployment roles if the source server has deployment options associated
with it: you must remove all deployment options before moving the roles. Because
you cannot remove deployment roles associated with a server in Read-Only mode
you use this feature to move roles between other DNS servers or servers in
Read-Write mode.
Note: When creating a Primary DHCP deployment role,
selecting a Secondary Server Interface for failover will create a Secondary DHCP
deployment role on the secondary server. Secondary DHCP deployment roles cannot
be moved with the Move Deployment Roles feature.
Warning: If a
primary DNS Deployment Role server interface changes, associated secondary DNS
Deployment Roles must be updated accordingly. For example, if a Primary DNS
Deployment Role is moved from one BlueCat DNS/DHCP Server to another BlueCat
DNS/DHCP Server with a different services IP address, associated Secondary DNS
Deployment Roles must be updated manually to use the new IP address for zone
transfers.
To move a deployment role: