Data Node information - Adaptive Applications - BlueCat Gateway - 23.2.3

BlueCat Distributed DDNS Administration Guide

Locale
English
Product name
BlueCat Gateway
Version
23.2.3
Before you configure the data node information in the Distributed DDNS Application Node, make sure that you have at least one data node deployed. For more details on deploying data nodes, see Deploying Distributed DDNS Data Nodes on BDDSes.

Service status

Within the Manage DB Nodes table, a settings icon (a gear) appears for each service on a node. The colour indicates the current status of that service.

The possible status for each service is as follows:
Status Icon
Started
Stopped
Unknown/Error
Starting
Stopping
Note: The Distributed DDNS UI checks the status of each service every 3 minutes. That means it can take up to 3 minutes for a change in status to be reflected in this page.

Configuring services on the data node

To configure a specific service, click the Settings gear icon under the column for the service that you want to configure:
  • MariaDB: Manages the database service on a single data node. You can stop the database backup service on the nodes or change the configuration.
    Note: If there are fewer than three nodes in the database cluster, you cannot stop the database service.
  • Auto Backup: Manages the automated backup service that runs on one of the data nodes. This service periodically backs up the database using the backup settings configured in the Application node's Configuration information settings.

    Tip: If the data node with the Auto Backup service shuts down, another data node in the cluster will automatically start the Auto Backup service to replace it.
    Note: You cannot stop this service if there is only one running node in the database cluster.
  • Auto Scavenging: Manages the scavenging service that automatically runs on one of the data nodes. This service periodically removes stale resource records from the database and DNS server, using the aging and scavenging settings configured in the Configuration section of the DNS Zone or Reverse DNS pages.

    Tip: If the data node with the Auto Scavenging service is shut down, another data node in the cluster will automatically start the Auto Scavenging service to replace it.
  • Disk Monitor: Manages the disk monitoring service that runs on each data node. If the used disk space on a node exceeds 95%, the service turns off the Enable Logging Update Records in the Configuration tab. While this setting is turned off, the Distributed DDNS service does not write new DNS updates to the database.

  • Sync Data: Manages the service that synchronizes Address Manager information to the Distributed DDNS database.

    Note: This service runs on only one database node. If the data node with the Sync Data service is shut down, another data node in the cluster will automatically start the Sync Data service to replace it.
    This service synchronizes the following information with the Distributed DDNS database:
    • Address Manager replication information: If an Address Manager failover occurs and the IP address of the primary server changes, the service detects the change and updates configuration information to use the IP address of the new primary server.
    • Address Manager zone information: When changes in zone information are detected, (such as DNS servers and TSIG keys), those changes are updated in the Distributed DDNS database. By default, the service checks for zone information changes every 30 seconds.
    • Resource Record information about added zones: When changes in resource records for added zones are detected, those changes are updated in the Distributed DDNS database. By default, the service checks for zone information changes every 120 seconds (2 minutes).
    Note: You cannot stop the Sync Data service if there is only one running instance in the database cluster.

Clicking the Settings gear icon for a service opens the service's configuration window. You can add details related to that service within that configuration window.



  1. Service name: The name of the service that you are configuring.

  2. Service action: Actions that can be performed on the service:

    • Start: Start the service. This field is disabled when the service is started.

    • Stop: Stop the service. This field is disabled when the service is stopped.

    • Refresh Log: Refresh the log information.

  3. Service configuration: Enter the configuration information for that service.

    Note: You can only edit the configuration information when the service is stopped.
  4. View Log: Display the last 1000 lines of the log information for a service.

    • On the View Log tab, you can select the log level to specify the type of logging content to display.

    • You can click the Refresh Log button to reload the log content.

Adding a data node



  1. Click to add a new data node.

  2. In the Name field, enter the name of the data node. This name must be unique and does not have to match the docker container name of the Distributed DDNS Data Node.

  3. In the IPv4 Address field, enter the IPv4 address of the data node.

  4. In the IPv6 Address field, enter the IPv6 address of the data node.

  5. Click Add to add the data node to the Distributed DDNS Application Node.

Updating a data node configuration

  1. Click the name of an existing data node.

  2. In the Name field, enter the updated of the data node. This name must be unique and does not have to match the docker container name of the Distributed DDNS Data Node.

  3. In the IPv4 Address field, enter the updated IPv4 address of the data node.

  4. In the IPv6 Address field, enter the updated IPv6 address of the data node.

  5. Click Save to save the updated settings.

Deleting a data node configuration

  1. Click the row of a service node that you wish to delete.

  2. Click to delete the selected data node. A window appears confirming that you would like to delete the data node.

    Note: If the Distributed DDNS Application Node cannot connect to the data node, you can forcefully remove the node by selecting the override option.
  3. Click OK to confirm the data node deletion.

Downloading data node diagnostic data

You can download all configuration and log files by clicking next to the data node.

You can also forward service logs to a remote ArcSight server. For more information, refer to Configuring log forwarding on Service Nodes.