Three systems. Zero drift.
DNS, DHCP, and IPAM drift apart because they are three databases pretending to agree. XonDDI collapses them into one record of truth with derived views. Drift is not detected and fixed. It cannot occur.
01 — Capabilities
Authoritative · Dynamic · Automated
/01
Authoritative DNS
Zones · DNSSEC
Zone and record management with AXFR import and managed DNSSEC signing. Key ceremonies handled by the platform, not a wiki page.
/02
DHCPv4
Scopes · Leases · Fingerprinting
Scope management, lease tracking, device fingerprinting, and static reservations bound to the same records IPAM sees.
/03
DHCPv6 & prefix delegation
PD pools · Lifetimes
Prefix delegation pools with lifetime and renewal management. Dual-stack rollouts without parallel bookkeeping.
/04
Lease archival
Cold storage · Compliance
Historical leases archived to cold storage with retention policies. When the lawful-intercept request arrives, the answer exists.
/05
Server federation
ISC · Kea · Microsoft · Cloud
Registry of upstream DNS and DHCP servers with bidirectional sync. Adopt incrementally; retire legacy servers on your schedule.
/06
Reverse-PTR automation
Zero manual PTRs
PTR records created and retired automatically on IP assignment and release. The chore nobody does reliably, done reliably.
02 — The core idea
Drift, removed structurally
/01
Not synchronised.
Derived.
Legacy stacks run three databases and a prayer of sync jobs. XonDDI stores one record; DNS answers, DHCP scopes, and IPAM views are projections of it. A record cannot disagree with itself. That is the entire trick, and it removes a whole category of outage.
IMG-DDI-PHOTO
21:9 · fiber distribution photograph
IMG-DDI-PHOTOXonware · field documentation
03 — What that buys
Structural guarantees
3→1
Systems collapsed to one record
0
Sync jobs between DNS, DHCP, IPAM
100%
PTR records automated
4+
Server families federated