System Requirements for Linux-based DNS and DHCP Servers

Hardware requirements for Management UI Console - Main server

Hardware requirements for Discovery Node Agent

Hardware Requirements for Management UI Console - Main Server

Based on your network requirements in terms of zones or subnets, the hardware requirements to install DDI Central's Management UI Console vary to ensure optimal performance. Select a tab to view the recommended hardware configurations tailored to different scales of network size and complexity.The following hardware requirements are mandatory for the server running the Management UI Console:

Zones < 15 or Subnets < 15

Zones > 15 - 100 or Subnets > 15-100

Zones > 100 to < 300 or Subnets > 100 to < 300

Zones > 300 or Subnets > 300

Parameter	Essential/Professional
Processor	8 CPU Core
RAM	12 GB
HDD	500 GB
Operating System	64 bit

Parameter	Essential/Professional
Processor	8 CPU Core
RAM	16 GB
HDD	500 GB
Operating System	64 bit

Parameter	Essential/Professional
Processor	16 CPU Core
RAM	32 GB
HDD	1 TB
Operating System	64 bit

Parameter	Essential/Professional
Processor	32 CPU Core
RAM	64 GB
HDD	1 TB
Operating System	64 bit

Hardware Requirements for Discovery Node Agent

DDI Central's Discovery Node Agent is a small, lightweight agent that must be installed on all your existing ISC-DNS and ISC-DHCP clusters for continous visibility.

Based on your network requirements in terms of zones or subnets, the hardware requirements to install DDI Central's Discovery Node Agent vary to ensure optimal performance. Select a tab below to view the recommended hardware configurations tailored to different scales of network size and complexity.The following hardware requirements are mandatory for the server running the Discovery Node Agent:

Zones < 15 or Subnets < 15

Zones > 15 - 100 or Subnets > 15-100

Zones > 100 to < 300 or Subnets > 100 to < 300

Zones > 300 or Subnets > 300

Parameter	Essential/Professional
Processor	8 CPU Core
RAM	12 GB
HDD	500 GB
Operating System	64 bit

Parameter	Essential/Professional
Processor	8 CPU Core
RAM	16 GB
HDD	500 GB
Operating System	64 bit

Parameter	Essential/Professional
Processor	16 CPU Core
RAM	32 GB
HDD	1 TB
Operating System	64 bit

Parameter	Essential/Professional
Processor	32 CPU Core
RAM	64 GB
HDD	1 TB
Operating System	64 bit

Software Requirements

Software	Minimum Versions Required for Evaluation	Version Requirements for Production
Linux OS	Ubuntu 24/ Debian 12 and above	Ubuntu 24/ Debian 12 and above
Browsers	Chrome/ Firefox/ Edge	Chrome (preferred)/ Firefox/ Edge

Software Libraries Required

OpenSSL for secured network communication
Sudoers file for user authorizations
libxml2 version 2.9.1 or higher
libxmlsec1 version 1.2.33 or higher
libnss3
libcap

Linux distributions' Specific Packages:

Ubuntu:

libjpeg-dev
libjpeg62-dev

Debian:

libjpeg-dev
libjpeg62-turbo

RHEL/Fedora:

libjpeg-turbo
libjpeg-turbo-devel

Port Requirements

Port Name	Default Port Numbers	Protocol	Usage	Connection
Web server port	9090	TCP	Used to connect to DDI Central's Management UI Console server from a web browser	Inbound
Embedded database port	33306	TCP	Used to connect to the PostgreSQL database in DDI	N/A
HTTPS Port	9443	TCP	Used for DDI Node Agent communication and connecting the web console	Bidirectional
Web Socket	8001	TCP	Enables real-time updates and live monitoring between DDI Central and connected servers.	Bidirectional

Database Requirements

PostgreSQL comes bundled with the product.

Note: In case of failover, please use PostgreSQL with replication configured.

Network Port Configurations

To ensure seamless communication and operation of DDI Central and its managed DNS and DHCP services, configure the following network ports as required:

DNS (Domain Name System)

TCP and UDP Port 53 (DNS): Must be open for DNS query and response traffic. TCP port 53 is also required for operations such as DNS zone transfers.

DHCP (Dynamic Host Configuration Protocol)

UDP Port 67 (DHCP Server): Must be open for the DHCP server to receive DHCP requests from clients.
TCP Port 647 (DHCP Failover): Must be open for communication between primary and secondary DHCP servers configured as a failover pair.
TCP Port 8000 (Kea Control Agent): Must be open to enable communication with the Kea Control Agent for remote configuration and management of Kea DHCP services.
Port 53001 (Kea DHCP-DDNS): Must be open to enable communication between Kea DHCP services and the Kea DHCP-DDNS service for Dynamic DNS updates.
TCP Port 8005 (Kea DHCP High Availability): Must be open for bidirectional communication between Kea DHCP servers configured as a high-availability pair.
Note: If port 8005 is configured for DHCPv4 high-availability communication, use a different available port, such as 8006 or 8007, for DHCPv6 high-availability communication, and ensure that the corresponding port is also permitted through the firewall.

Ensure that firewalls and other network security controls are configured to permit the required traffic between the corresponding DDI Central components and managed servers.