DNS — Names
The resolver laptops already ask, and the zones that hold A/PTR. Lattice is not that resolver unless you publish lattice-dns on purpose. A worker writes names after Ack into AD, BIND, or PowerDNS.
DDI
Three jobs. Software-only, on-prem. Keep the DNS you already run. Meter is managed IPs, not prefix size. phpIPAM and NetBox hold a plan — they do not Offer. Infoblox and BlueCat are appliances; Lattice is not. Windows DHCP Offers — the spreadsheet is still the used list. Lattice puts the plan and the grant in one catalog.
The resolver laptops already ask, and the zones that hold A/PTR. Lattice is not that resolver unless you publish lattice-dns on purpose. A worker writes names after Ack into AD, BIND, or PowerDNS.
Who gets which address, for how long. Windows DHCP, ISC dhcpd, and Kea do this. phpIPAM and NetBox do not.
Prefixes, subnets, reservations, the used list. A spreadsheet, phpIPAM, or NetBox can hold a plan. If DHCP does not read those rows, the plan is a comment.
A reservation in phpIPAM is a comment until something syncs it. NetBox is a DCIM/CMDB: racks, cables, and an addressing plan. Lattice can import missing prefixes from NetBox; it does not let NetBox delete a live pool. phpIPAM vs DHCP · NetBox.
Windows DHCP, ISC dhcpd, and Kea hand out addresses. The used list lives somewhere else — MMC plus a sheet, conf plus the lease file, JSON plus Stork. That split is the Tuesday. Replace Windows DHCP · Replace ISC dhcpd · Replace Kea.
Software-only, on-prem Ubuntu tarball. Prefixes, subnets, pools, reservations, and leases are one catalog; dhcpd serves those rows. DNS is an adapter — keep the resolver you already run. Infoblox and BlueCat are appliances; Lattice is not. Not 24×7. Meter is managed IPs, not prefix size. How it works · Infoblox alternative.