Replacing the server sending Secondary Zone Notifications - BlueCat Integrity - 26.1.0

Address Manager Administration Guide
ft:locale
en-US
Product name
BlueCat Integrity
Version
26.1.0

Replace the server sending Secondary Zone Notifications to Address Manager.

Prerequisite: The replacement BlueCat DNS/DHCP Server must be under Address Manager control.
Attention: BlueCat strongly recommends scheduling a maintenance window during non-peak times when performing this task, as a gap in secondary zone notifications will occur. Once the following steps have been completed, all Secondary Zone Notifications, including missed Secondary Zone Notifications, will be visible in Address Manager.

To replace the server selected to send Secondary Zone Notifications to Address Manager:

  1. Navigate to the configuration, view, or zone level where the Secondary Zone Notifications deployment option is configured.
  2. Select the Deployment options tab.
  3. Select the row containing the Secondary Zone Notifications option in the Deployment options table, then select Edit in the expanded details section.
  4. Under Servers, select the replacement BlueCat DNS/DHCP Server.
  5. Under Change Control, add comments if required.
  6. Select Save.
  7. Delete the zone associated with the secondary DNS/DHCP Server you want to replace. For more information about deleting DNS zones, refer to Deleting a DNS zone.
  8. Add a new zone to be associated with the replacement secondary DNS/DHCP Server. For more information about adding a zone, refer to Creating DNS zones.
  9. Add a secondary deployment role to the replacement DNS/DHCP Server and a primary deployment role to the RFC-compliant server. For more information about adding DNS deployment roles, refer to Adding DNS deployment roles.
    Note: The primary role must be assigned to an Other DNS server.
  10. Configure a Secondary Zone Notifications option on the replacement DNS/DHCP Server secondary. For more information about configuring the Secondary Zone Notification option, refer to Configuring the Secondary Zone Notifications deployment option in Address Manager.
  11. Deploy DNS.
    Note: A full deployment must be performed to the affected DNS/DHCP Server in order for your changes to take effect.