Prerequisites and limitations - Adaptive Applications - BlueCat Gateway - 23.2.3

BlueCat Distributed DDNS Administration Guide

Product name
BlueCat Gateway

Before you begin, ensure that the following prerequisites are met.

Software Prerequisites

  • Address Manager v9.3.x, v9.4.x, or v9.5.x

  • DNS/DHCP Server v9.3, v9.4.x, or v9.5.x acting as a primary server.

Hardware Prerequisites

  • Multiple BDDSes to provision the Distributed DDNS Data Nodes, Distributed DDNS Application Node, and the Distributed DDNS Service Nodes.

  • At least 2 CPUs and 8GB of RAM allocated to the BDDS.

  • At least 50GB of free disk space on the BDDS.

Configuration Prerequisites

You must configure the BlueCatGateway UDF and a BlueCat Gateway user on Address Manager. For more information, see Configuring BlueCat Gateway in the BlueCat Gateway Administration Guide.

User Account Permission Prerequisites

  • A Quay account that has been granted access to the BlueCat Distributed DDNS Adaptive Application or a local account where docker can pull the Adaptive Application.

  • An Address Manager Administration account with both GUI and API access for installing and setting up BlueCat Distributed DDNS. This account must have access rights to any resources on which actions be performed, such as DNS zones, IP blocks, IP networks, and servers.


Distributed DDNS has the following limitations.

  • Record and zone capacity limits: The Distributed DDNS system supports systems with a maximum of 1 million resource records and 500 zones. Exceeding these limits can cause errors in the functioning of Distributed DDNS and messages might not be correctly processed.

  • When installing and configuring Data Nodes, the database password must contain only letters and numbers. It cannot contain special characters like @, #, or !. Use of special characters may cause errors in deployment of the Distributed DDNS system and cause it to function abnormally.

  • After adding new zones, the Distributed DDNS system needs to synchronize all the data between nodes in the system in order to successfully process dynamic updates. You can see whether the synchronization process has completed in log messages for the Data and Service nodes. For more details, see Making sure that data is synchronized between Distributed DDNS nodes.