Redeploying a Distributed DDNS Database Node on a BDDS - Adaptive Applications - BlueCat Gateway - 23.2.4

The following procedure describes how to redeploy an existing Distributed DDNS Database Node on a BlueCat DNS/DHCP Server (BDDS).

1. Gracefully stop the running container. To do so, run the following command:

   docker stop -t 90 <Running container name>

   By stopping the container gracefully, you make sure that all processes are properly terminated. This is especially important for the MariaDB database process, which typically requires more than 10 seconds to properly exit.

2. After you gracefully stop the container Before you begin, remove the running container on the Database Node. To do so, on the host server of the Database Node, run the following command:

   docker rm –f <running-container-name>

3. Log in to the BlueCat Gateway instance of the Distributed DDNS Application Node.

4. Under Available Actions, click Distributed DDNS, then click the DDNS Deployment tab.

5. Within the list of BDDS servers, select the name of the server whose database node you want to redeploy.

6. Within the Configure Remote Services window, in the Service Type section, select Database Node.

   If a database node is already deployed, you will be warned that the Database service is already enabled, and that the database service will be re-deployed (rather than deployed to that node for the first time).

7. Click Continue.

8. In the window that appears, in the General section, enter the following information:

   • Authentication Type: Select the method of authentication. You can select Password or SSH Key.

     If you select Password, enter the following information:

     • SSH Username: Enter the username that will be used to establish an SSH connection with the BDDS.
     • SSH Password: Enter the password that will be used to establish an SSH connection with the BDDS.
     If you select SSH Key, enter the following information:

     • SSH Username: Enter the username of the root or non-root user. If entering a non-root username, it must also be added to the /etc/sudoers file. You can use the following commands to add non-root username to the file:

       sudo visudo
       <non-root_username> ALL=(ALL) NOPASSWD: ALL

     • SSH Private Key: Enter the SSH private key produced using the ssh-keygen command. Ensure that the corresponding public key is available on the destination server using the following commands:

       ssh-keygen
       ssh-copy-id -i <public_key_file> <remote_user>@<remote_server>

     • Key Passphrase: Enter the key passphrase if one was used when generating the SSH key pair.

   • Database Cluster: Enter the name of the database cluster.

     Warning: This name should be the same cluster name used previously by the Database Node.

   • Database Password: Enter the password for the default user of the database cluster. By default, the password is ddns_admin.

9. In the Repository section, enter the following information:

   • Image: Enter quay.io/bluecat/distributed_ddns_database:23.2.4
   • Username: Enter your Quay username.
   • Password: Enter your Quay password.
10. When you're done, click Deploy.