Replace a Designate Node
Problem
One or more hosts authorized with the Designate role need to be decommissioned, shutdown, or otherwise replaced.
If this has already occurred, one or more zones and their respective recordsets may be showing in either PENDING or ERROR state, depending on how long it's been.
Environment
Platform9 Managed OpenStack - All Versions
Designate
Procedure
Identify the IP address of your BIND server, and also of the Designate host(s) which are to remain or otherwise replace the old hosts.
Create a file update-masters.awk on the BIND server and populate it with the following content, modifying the bolded variables as per the legend below.
SERVER_IP = IP on which the BIND server is listening.
MASTERS = IP(s) of the aforementioned Designate host(s) which will remain to be online and become the active masters.
Execute the awk script and pipe the stdout to update_zones.sh.
Set the proper permissions and execute the resulting update_zones.sh script.
Note: Afterward, it may take approximately 5-10 minutes for the DNS zones to update and reflect an ACTIVE status once again. If this does not occur, attempt to create a new DNS record or otherwise create an instance on a provider network or tenant network with a floating IP, either of which would automatically provision a DNS record (based on your Designate configuration). Once a new record is added, the zone and respective recordsets should show ACTIVE.
