Kea DHCP management at scale with a unified DDI control plane

Kea DHCP is a modern, open-source DHCP server developed by Internet Systems Consortium (ISC) for managing IPv4 and IPv6 address assignment. It uses separate DHCPv4, DHCPv6, and Dynamic DNS components and provides APIs that allow external management systems to retrieve information, modify configurations, and automate DHCP operations. Kea also supports database-backed leases, reservations, and selected configuration data, making it well suited for modern and distributed network environments.

Kea DHCP can be centrally managed by connecting Kea servers to a management platform that provides a unified interface for configuration, visibility, and IP address management. ManageEngine DDI Central enables administrators to manage Kea-based Modern DHCP environments alongside DNS and IPAM operations. Administrators can create, configure, and delete DHCPv4 and DHCPv6 subnets, static subnets, hosts, and DDNS configurations from a centralized management console.

For multi-server environments, a centralized DDI approach can simplify Kea DHCP management by bringing server configuration, DHCP scopes, leases, IP address information, monitoring, and administrative controls into a common operational view. Instead of treating every DHCP server as a separate configuration island, DDI Central provides consolidated visibility across clusters and IP spaces, helping administrators manage growing and geographically distributed DHCP environments more consistently.

You can manage Kea DHCP through graphical management tools rather than working exclusively with configuration files or API calls. ISC provides Stork for Kea monitoring and management, while ManageEngine DDI Central provides a broader DDI management layer that brings Kea DHCP together with IPAM, DNS, scope management, administrative controls, reporting, and network-wide IP visibility.

Kea DHCP can operate without an IPAM solution, but organizations managing large, distributed, or rapidly changing IP environments can benefit significantly from integrating DHCP with IPAM. IPAM provides the wider context around the addresses being assigned—such as subnet capacity, IP utilization, static addresses, VLANs, hierarchical IP space, and lease information. DDI Central combines these IPAM capabilities with DHCP management so administrators can understand not only how addresses are allocated, but how the entire address space is being used.

Kea DHCP and IPAM can be integrated through a DDI management platform that correlates DHCP scopes and leases with the organization’s broader IP address inventory. With DDI Central, administrators can manage Kea DHCP while using IPAM views to understand subnets, static IP space, address availability, utilization, leases, supernets, VLANs, and the relationships between different parts of the network. This gives DHCP operations the IP context required for capacity planning and more informed address management.

No. ISC published the final maintenance releases in October 2022 and set end-of-life for that December. The daemon still runs and some distributions still ship it, but there is no feature work and no routine maintenance, and ISC's own recommendation is to migrate to Kea.

Not at the file level — it's a different implementation with different configuration, so a dhcpd.conf has to be translated rather than copied. What clients see on the wire is unchanged. In DDI Central you don't do that translation by hand: the server's objects are already modelled in the platform, so you switch its DHCP engine from legacy ISC DHCPD to Modern (Kea) in the settings page, enter the Kea interface details and save.

Yes, provided they're authoritative for different subnets or relay targets. Most teams run both through the middle of a migration and keep the legacy server serving whatever hasn't moved yet. In DDI Central, ISC DHCPD and Kea should run in separate clusters.

Kea provides the modern DHCP engine; a DDI solution provides the operational layer around it.

A DDI platform brings DNS, DHCP, and IP address management together so network teams can manage address allocation in the context of DNS records, IP inventory, static addresses, utilization, access controls, auditing, monitoring, and reporting.

This becomes increasingly useful as the number of DHCP servers, subnets, locations, and administrators grows.

Kea gives you modern DHCP. DDI Central turns it into modern DDI.

DDI Central supports Kea as its Modern DHCP service for both DHCPv4 and DHCPv6 environments.

From DDI Central, network administrators can create, configure, and delete Kea subnets, static subnets, hosts, and DDNS configurations. DDI Central also places Kea DHCP within a broader DDI environment that includes IPAM visibility and centralized administration.

Yes. DDI Central supports Kea-based Modern DHCP for both DHCPv4 and DHCPv6.

This enables organizations moving to Kea to manage both address families through a centralized DDI environment instead of treating IPv4 and IPv6 operations as separate management silos.

In Kea, DHCP address allocation is organized primarily around subnets and address pools. Administrators define the subnet, pools of addresses available for dynamic allocation, DHCP options, reservations, lease parameters, and other policies required for clients.

When Kea is managed through DDI Central, administrators can create and configure DHCPv4 and DHCPv6 subnets through the management interface, bringing scope configuration into the same operational environment as IPAM and other DDI services.

Kea supports host reservations that associate client identifiers such as MAC addresses, DUIDs, or other identifiers with predefined addressing or DHCP configuration.

Unlike legacy ISC DHCP, where host reservations were global, Kea supports subnet-specific reservations by default and can also support global reservations.

DDI Central enables administrators to create and manage hosts within Kea-based Modern DHCP environments from its centralized interface.

Kea can use its DHCP-DDNS component to coordinate dynamic DNS updates when DHCP clients receive or release addresses.

DDI Central supports DDNS configuration as part of its Kea Modern DHCP management, allowing DHCP and DNS workflows to be administered within a broader DDI environment rather than managed as isolated network services.

Effective Kea DHCP monitoring should look beyond server status and include DHCP leases, subnet utilization, address availability, and the overall health of the IP space.

DDI Central provides DHCP and IPAM visibility, including subnet utilization information, lease-related insights, alerts, and consolidated views of scopes and IP space. This helps administrators detect capacity issues and understand how DHCP consumption affects the wider network.

Kea exposes an API that allows external applications to query and modify a running Kea server, making it suitable for automated and API-driven management workflows.

A DDI management platform can build operational workflows around these capabilities by centralizing configuration changes, repeatable administration, IP management, and policy-based operations. DDI Central also provides scheduling capabilities for supported DHCP configuration objects, allowing network changes to be planned for predetermined times.

Static IP addresses should be managed alongside DHCP leases so administrators can see both dynamically assigned and manually configured addresses within the same IP space.

DDI Central provides static subnet and static lease management. Its Auto Lease Update capability can periodically ping addresses within a static subnet to determine whether they are reachable and update their status, helping administrators discover and track devices that use manually assigned static IPs.

Multi-site Kea deployments can be managed more efficiently when DHCP infrastructure is grouped into a centralized management and IPAM hierarchy.

DDI Central provides site, cluster, supernet, subnet, and IP-space views and a Unified View for consolidating DHCP scopes across managed clusters. This makes it easier to understand DHCP address space across branches, data centers, and other distributed environments from a common interface.

Kea DHCP is ISC's modern DHCP implementation and is architecturally different from the legacy ISC DHCP server.

Kea provides separate DHCPv4, DHCPv6, and DDNS components, extensive APIs, database integration options, multithreading, and an HA model for IPv4 and IPv6. ISC DHCP reached end of maintenance in 2022, while Kea continues as ISC's actively developed DHCP platform.

Organizations should consider migration because ISC DHCP has no longer been maintained by ISC since 2022, while Kea is the modern DHCP platform ISC continues to develop.

Kea also introduces architectural advantages such as APIs for integration and online reconfiguration, multithreading, database-backed data, modular services, and HA support for both DHCPv4 and DHCPv6.

Modern DHCP is DDI Central's support for Kea DHCP. It brings Kea-based DHCPv4 and DHCPv6 into the same operational view as DNS, IPAM, monitoring, automation, and access control.

Kea provides the high-performance DHCP engine. DDI Central adds the fleet-wide operations layer: unified visibility, IPAM, scheduled change, analytics, RBAC, auditing, and monitoring.

Yes. Reachable Kea servers across branches, campuses, data centers, and remote sites can be onboarded and managed through one console.

Yes. Administrators can manage pools, leases, reservations, IPv6 address space, and prefix delegation in one operating model.

Yes. Live DHCP logs can be streamed and filtered in the console, then delegated through role-based access without granting shell access.

On an existing managed server, switch its engine from Legacy ISC DHCPD to Modern Kea and supply the interface details. You can also import DHCPv4, DHCPv6, and DDNS configuration files separately.

Two routes. Point DDI Central at a running Kea server and it discovers and models the existing subnets, pools, options, reservations and leases without changing anything on the host. Or import the configuration files directly — DHCPv4, DHCPv6 and DDNS imported separately — which is the route to take when you're migrating an inherited configuration or building a new cluster from a known-good file.

Yes. Rsyslog is configured for your DHCP servers from the interface rather than by editing files on each host, and live logs stream into the console. An engineer can filter the stream by client and watch an exchange succeed or fail in real time, and log access is delegated through role-based access control — so helpdesk staff get the visibility without getting a shell.

It does. ISC's testing found Kea's lease rate falls once pool utilisation reaches around 96 percent, because finding a free address costs more effort as the pool fills. Headroom is a performance setting, which is why utilisation tracking and capacity forecasting belong in the same console as the DHCP configuration rather than in a separate spreadsheet.

Yes, through kea-dhcp-ddns, a dedicated daemon that takes name change requests from the DHCP servers and sends forward and reverse updates to DNS, with TSIG support. DDI Central configures both ends of that relationship for you.

In most deployments, yes. The Kea DHCPv4 and DHCPv6 servers are CPU-intensive and run multi-threaded — on by default from Kea 2.4.0 — so throughput scales with the cores you give them instead of being capped by a single process. ISC's own testing recorded higher lease rates with multi-threading in every configuration measured, with memfile the fastest lease backend. Kea's high availability also defaults to multi-threaded operation over a direct peer connection, removing a bottleneck that existed in earlier versions.

Because config files don't schedule themselves, don't record who changed what, don't tell you a subnet is 91% full, and don't notice that a reservation has been pointing at a decommissioned server for eleven months. DDI Central adds the scheduling, audit, reporting, IPAM and lease-tracking layer around Kea that operations teams need once the estate grows past a couple of servers.

Yes. It unifies DNS, DHCP and IPAM across Linux, Windows, and CISCO IOS(XE/XR) environments, so Kea servers, BIND, Microsoft DNS and DHCP, and your address space are all managed from one console rather than four.

A successful ISC DHCP-to-Kea migration should consider configuration compatibility, DHCP options, host reservations, lease migration, DDNS behavior, high availability, database architecture, monitoring, and how Kea will be managed after migration.

Kea is not simply a renamed version of ISC DHCP; it uses a different architecture and configuration model. For example, reservation behavior and option scoping can differ, so migrated configurations should be reviewed and tested carefully.

It is also worth planning the management layer at the same time. Moving to a modern DHCP engine is an opportunity to consolidate DHCP with IPAM, DNS visibility, automation, auditing, and multi-site management rather than reproducing a legacy management model on a new server.