Skip to content

SpatiumDDI in five minutes

  1. Add a subnet
  2. Turn on DHCP
  3. Add a printer
  4. Check DNS
  5. See the audit trail

Interactive tour · about 3 minutes

DNS, DHCP and IPAM.
One place.

Give a new VLAN its subnet, DHCP and a printer with DNS records, on a real SpatiumDDI. You make the clicks.

23 steps · mouse, touch or keyboard (→ next, ← back)

Recorded on SpatiumDDI 1.0.0-beta.3

Every service on your network depends on DNS and DHCP, and both depend on knowing which address belongs to what. This short video shows what goes wrong when the three are kept apart, and how SpatiumDDI keeps them together.

▶ Why DNS, DHCP and IPAM belong together · 1:38 · narrated, captions on (CC) · recorded on SpatiumDDI 1.0.0-beta.3
Transcript

0:00Every device on your network needs an address, and a name that points to it.

0:06In most networks, those live in three places: a DHCP server, a DNS server, and a spreadsheet that tries to keep up with both.

0:16Three copies of the truth. And sooner or later, they disagree.

0:21Two devices land on the same address. A retired server's name still resolves. A pool runs dry, and nobody sees it coming.

0:31When either DNS or DHCP stumbles, everything built on them stumbles too: sign-in, email, and every app your users rely on.

0:41SpatiumDDI keeps all three in one place. Your address plan is the record, and DNS and DHCP are built from it.

0:50Allocate an address, and its forward and reverse DNS records are written in the same step. Within seconds, your DNS servers have them.

0:59If the control plane goes down, your DNS and DHCP servers keep answering from their last good configuration. Changes wait. Your network doesn't.

1:10Every change lands in a tamper-evident audit log, and deletes go to Trash first, so a mistake can be undone.

1:17It's open source, it runs on your own hardware, and it drives BIND9, Kea, PowerDNS, Windows DNS and DHCP, and cloud DNS.

1:28See it for yourself in the free SpatiumDDI Academy, with a hands-on lab that runs on your own laptop.