Replace the server sending Slave Zone Notifications to BAM.
Prerequisite: The replacement BlueCat DNS/DHCP Server must be under BAM 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 Slave Zone Notifications, including missed Slave Zone Notifications, will be visible in BAM.
To replace the server selected to send Slave Zone Notifications to BAM:
- 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.
- Navigate to the level that the Slave Zone Notifications deployment option is configured.
- Click the Deployment Options tab.
- Under Deployment Options, click Slave Zone Notifications.
- Click the Slave Zone Notifications drop-down menu and select Edit.
- Under Server, select the replacement BlueCat DNS/DHCP Server in the Specific Server field.
- Under Change Control, add comments if required.
- Click Update.
- Delete the zone associated with the secondary BDDS you want to replace. For more information about deleting DNS zones, refer to Deleting a DNS zone.
- Add a new zone to be associated with the replacement secondary BDDS. For more information about adding a zone, refer to Adding DNS zones .
Add a secondary deployment role to the replacement BDDS
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.
- Configure a Slave Zone Notifications option on the replacement BDDS secondary. For more information about configuring the Slave Zone Notification option, refer to Configuring the Slave Zone Notifications deployment option in Address Manager.
Note: A full deployment must be performed to the affected BDDS in order for your changes to take effect.