Updating the Distributed DDNS Service Node - Adaptive Applications - BlueCat Gateway - 22.1

BlueCat Distributed DDNS Administration Guide

Product name
BlueCat Gateway

Before you begin

You must stop the DDNS receiver and isolate it from a production environment to ensure that no additional messages are sent during the upgrade. This can be done from the Distributed DDNS Application Node UI. For more information, refer to Service Node information.

When the DDNS receiver service is stopped, there are typically no messages in the Queue. If there are any messages in the queue, the processor log should be checked for additional information.

Performing the DDNS service update

  1. Click the next to the database node that you would like to upgrade. The Upgrade DDNS Node window opens.
  2. Within the Authentication section, select either Password or SSH and provide the corresponding authentication information.
  3. Under Repository, enter the following information:
    • Image: enter the default URL for the database Docker image
    • User and Password: enter your Quay or local repository username and password.
  4. Click Upgrade.
During the upgrade process, the system performs checks and periodically asks you to confirm the following information:
  • Check for the current number of update messages in the queue that have not been processed.
  • Check for the external client connections to the service node and show all client IP addresses.
  • Check for the outgoing connections from the service node and display their process IDs.

The upgrade process displays any errors reported and successful messages. Once the node has successfully installed the updated software, you can verify the upgrade status from the Service Nodes page.

If the node updated successfully, you can proceed to update the next node in the cluster.

After the upgrade

  • Check if the DDNS Receiver, DDNS Processor, and Queue Service started normally.