Migrating from ISC DHCP to Jagornet 5.0
With ISC DHCP officially End-of-Life, network engineers face a choice: endure the multi-daemon sprawl and hook complexities of Kea, or upgrade to a unified, single-service MPL 2.0 runtime with native gRPC High Availability and OpenAPI 3.0 REST.
Why ISC DHCP Users Are Looking Beyond Kea
ISC announced the End-of-Life of ISC DHCP (dhcpd) in late 2022. While ISC recommends Kea as its successor, many enterprise network teams discover that Kea introduces significant operational friction.
Legacy ISC DHCP
Deprecated, unmaintained, and increasingly vulnerable to unpatched security advisories.
- ❌ EOL since December 2022 (no CVE patches)
- ❌ Separate daemons for IPv4 and IPv6
- ❌ Proprietary, rigid config syntax
- ❌ Legacy OMAPI with limited tooling
ISC Kea DHCP
Modernized rewrite, but introduces architectural fragmentation and paywalled hook libraries.
- ⚠️ 4+ distinct daemons required (v4, v6, ctrl, ddns)
- ⚠️ High Availability requires external C++ hooks
- ⚠️ Advanced enterprise features locked behind paid subscriptions
- ⚠️ Heavy multi-process orchestration
Jagornet DHCP 5.0
A unified, single-service architecture built for cloud, containers, and modern enterprise networks.
- ✅ 100% MPL 2.0 Open Source Core (No paid hook paywalls)
- ✅ Single Unified Service (v4, v6, DDNS & REST in one)
- ✅ Native gRPC HA (Zero external hook dependencies)
- ✅ Java 21+ / Netty (Cross-platform Linux, Windows, macOS)
ISC DHCP to Jagornet Directive Mapping
How standard dhcpd.confconfiguration blocks and statements translate into Jagornet's validated configuration schema (available in YAML, JSON, or XML).
ISC DHCP Directive (dhcpd.conf) | Jagornet DHCP 5.0 Structure | Operational Architecture & Notes |
|---|---|---|
shared-network { ... }subnet 10.0.100.0 netmask 255.255.255.0 { ... } | links: linkList: - name: "Client Subnet" address: "10.0.100.0/24" | All subnets in Jagornet belong to a link, defined by CIDR notation (or local interface). Subnets support option inheritance and cloud relay options (RFC 3011 / RFC 3527). |
range 10.0.100.50 10.0.100.200; | v4AddrPools: poolList: - range: "10.0.100.50-10.0.100.200" | Configured under each link. Multiple distinct address pools are supported per subnet with per-pool policy overrides and client filter scoping. |
host printer-lab { hardware ethernet 00:11:22:33:44:55; fixed-address 10.0.100.25;} | v4AddrBindings: bindingList: - ipAddress: "10.0.100.25" chaddr: "001122334455" configOptions: ... | Static bindings associate a hardware address (chaddr) or DUID with an IP. Can be declared statically in configuration or managed dynamically via the OpenAPI 3.0 REST API. |
option routers 10.0.100.1;option domain-name-servers 1.1.1.1, 8.8.8.8;option domain-name "corp.com"; | v4ConfigOptions: v4SubnetMaskOption: ipAddress: "255.255.255.0" v4RoutersOption: ipAddressList: ["10.0.100.1"] v4DomainServersOption: ipAddressList: ["1.1.1.1", "8.8.8.8"] v4DomainNameOption: domainName: "corp.com." | Options are strongly typed and validated against IANA standards at startup (e.g., ipAddressList, domainName, opaqueData), preventing syntax regressions. |
default-lease-time 86400;max-lease-time 172800; | policies: policyList: - name: "v4.defaultLeasetime" value: "86400" - name: "v4.maxLeasetime" value: "172800" | Configurable globally or scoped locally within specific links. In DHCPv6, mapped to v6.preferredLifetime and v6.validLifetime. |
failover peer "dhcp-failover" { primary; address 10.0.0.2; peer address 10.0.0.3; peer port 647;} | policies: policyList: - name: "ha.role" value: "primary" (or "backup") - name: "ha.peerServer" value: "10.0.0.3" - name: "ha.peerPort" value: "9066" | Native gRPC High Availability with real-time active/standby state synchronization over TLS. Minimal configuration required—protocol defaults to grpc and update mode defaults to sync. |
key "ddns-key" { algorithm hmac-sha256; secret "[secret]";};zone example.com. { primary 10.0.0.2; key "ddns-key";} | policies: policyList: - name: "ddns.update" value: "server" - name: "ddns.domain" value: "example.com." - name: "ddns.server" value: "10.0.0.2" - name: "ddns.tsig.keyName" value: "ddns-key." - name: "ddns.tsig.algorithm" value: "hmac-sha256." - name: "ddns.tsig.keyData" value: "[secret]" | RFC 4703 and RFC 4704 compliant Dynamic DNS engine with TSIG authentication, configurable multi-strategy conflict resolution, and automatic hostname sanitization. |
class "cisco-phones" { match if substring( option vendor-class-identifier, 0, 5 ) = "Cisco";} | filters: filterList: - name: "cisco-phones" filterExpressions: filterExpressionList: - clientClassExpression: v4VendorClassOption: opaqueData: asciiValue: "Cisco" operator: "STARTS_WITH" | Clean declarative pattern matching (e.g. STARTS_WITH, EQUALS) replaces fragile byte-offset substring expressions. Supports User Class, Vendor Class, Option presence, and hot-reloaded MAC/DUID access lists. |
# ISC DHCP Subnet & Reservation Configuration
subnet 10.0.100.0 netmask 255.255.255.0 {
option routers 10.0.100.1;
option domain-name-servers 10.0.0.1, 10.0.0.2;
option domain-name "corp.example.com";
default-lease-time 86400;
max-lease-time 172800;
pool {
range 10.0.100.50 10.0.100.200;
}
}
host printer-lab {
hardware ethernet 00:11:22:33:44:55;
fixed-address 10.0.100.25;
}# Jagornet DHCP 5.0 Subnet & Binding Configuration
links:
linkList:
- name: "Corporate LAN"
address: "10.0.100.0/24"
policies:
policyList:
- name: "v4.defaultLeasetime"
value: "86400"
- name: "v4.maxLeasetime"
value: "172800"
v4ConfigOptions:
v4SubnetMaskOption:
ipAddress: "255.255.255.0"
v4RoutersOption:
ipAddressList:
- "10.0.100.1"
v4DomainServersOption:
ipAddressList:
- "10.0.0.1"
- "10.0.0.2"
v4DomainNameOption:
domainName: "corp.example.com."
v4AddrPools:
poolList:
- range: "10.0.100.50-10.0.100.200"
v4AddrBindings:
bindingList:
- ipAddress: "10.0.100.25"
chaddr: "001122334455"The 4-Phase Production Migration Roadmap
Follow this proven engineering methodology to transition critical network segments with zero downtime and zero client disruption.
Configuration Audit & Extraction
Inventory your current ISC configuration to distinguish standard declarative structures from dynamic conditional logic:
- Extract Declarative Objects:Subnets, shared networks, IP pools, option arrays, and static reservations map directly into Jagornet's YAML, JSON, or XML schema.
- Automate Boilerplate: Utilize configuration conversion scripts (or our automated migration utilities) to batch-convert large subnet topologies.
- Evaluate Dynamic Logic: Audit ISC
classstatements,matchexpressions, and vendor option spaces to map them into Jagornet's hot-reloading MAC/DUID filters and policy engine.
Side-by-Side Sandbox Validation
Verify lease assignment behavior on non-production test ports without needing root permissions or disrupting broadcast traffic:
- Unprivileged Testing: Start Jagornet DHCP on unprivileged ports (e.g.,
-4p 10067 -6p 10547) on an internal VM or staging container. - Simulate Transactions:Use Jagornet's bundled Netty-powered test client (
./bin/testclientv4) to simulate DORA (Discover, Offer, Request, Acknowledge) transactions against your migrated subnets. - Inspect Telemetry: Verify Prometheus metrics and OpenAPI logs to confirm correct option delivery and policy enforcement.
Database Selection & Lease Continuity Strategy
Determine your storage architecture and establish how active leases will transition:
- Pluggable Storage: Select PostgreSQL or MySQL for enterprise multi-node clusters, or SQLite for lightweight edge appliances.
- Lease Continuity (The Graceful Expiration Pattern):Rather than performing risky raw database imports from ISC's text-based
dhcpd.leases, reduce ISC DHCP lease TTLs to 1–2 hours several days prior to cutover. As leases expire naturally, clients seamlessly re-request and populate Jagornet's database without IP conflicts. - Ping-Before-Lease Verification:Enable Jagornet's ICMP echo verification policy to ensure no rogue or unexpired addresses are handed out during cutover.
Cutover Execution & High Availability Sync
Execute the cutover with instantaneous switch-level redirection and immediate failover protection:
- Router IP-Helper Redirection: Update your core routers and distribution switches (
ip helper-addresson Cisco/Arista, or DHCP relay on Juniper) to point to the new Jagornet server VIP or primary IP. - Activate Standby Node:Configure Jagornet's native gRPC Active/Standby replication on port 9066 with TLS authentication for real-time lease synchronization.
- Live Telemetry Monitoring:Monitor request rates, allocation latency, and lease pool utilization in real time via Jagornet's Prometheus exporter.
Planning a Large-Scale ISC DHCP Migration?
Whether you are migrating hundreds of subnets, translating complex vendor-class options, or modernizing an enterprise DDI architecture, work directly with the creator of Jagornet DHCP Server for guaranteed zero-downtime cutover.