IPAM

IP address management with region and CIDR hierarchy, plus reverse sync with DNS so every address stays identified.

IPAM · DNS · Networking · PostgreSQL · React

GitHub →

Problem

Spreadsheets and tribal knowledge leave networks with orphan IPs, conflicting assignments, and DNS records that no longer match reality. Finding who owns an address—or whether a PTR is wrong—takes too long during incidents.

What it solves

IPAM keeps a structured inventory:

  1. Region — geographic or organizational scope
  2. Network — CIDR range within a region
  3. IP address — allocation with owner, status, and notes

Operators allocate and reclaim addresses inside known ranges instead of guessing from DHCP or firewall dumps alone.

IPAM and DNS reverse syncIPAM inventoryRegion → CIDR → IPDNSforward + reverse PTR
Authoritative IP inventory kept aligned with DNS so addresses stay identified.

Reverse sync with DNS

Forward DNS names an address; reverse (PTR) ties an address back to a name. IPAM reverse sync keeps those records aligned with the inventory:

  • New or updated allocations propose matching DNS updates
  • Drift between inventory and DNS is visible as a first-class problem
  • Orphan PTRs and unnamed live IPs can be reconciled instead of ignored

The goal is authoritative identity: every managed address has a clear record in IPAM and a consistent story in DNS.

System shape

A web UI over a PostgreSQL-backed API manages regions, networks, and IPs. Maps and filters help operators see utilization. DNS sync is modeled as a bidirectional boundary—IPAM remains the source of truth for allocation; DNS remains the source of truth for resolution once synced.

Outcome

Fewer unknown addresses, fewer surprise conflicts, and a clear path from “what is this IP?” to owner and purpose.