Parent folderOpen Confluence

RWS Architecture article

DNS, DHCP, and IPAM

DNS, DHCP, and IPAM is the product-neutral architecture building block for authoritative DNS, DHCP, and IP address management. It states what DC 3.0 needs from this capability befo

  1. Typeabb
  2. Statuscandidate
  3. Domainnetwork
On this page
  1. ABB DNS, DHCP, and IPAM
  2. Summary
  3. Capabilities
  4. Constraints
  5. Service Description
  6. Roadmaps
  7. Landing Zones
  8. Interfaces
  9. Dependencies
  10. EIRA Alignment
  11. Available SBB's

ABB DNS, DHCP, and IPAM

Summary

DNS, DHCP, and IPAM is the product-neutral architecture building block for authoritative DNS, DHCP, and IP address management. It states what DC 3.0 needs from this capability before a concrete SBB, product, or operating model is selected.

Capabilities

  • Provides authoritative DNS, DHCP, and IP address management.
  • Defines the functional, technical, security, and quality expectations that SBBs must satisfy.
  • Keeps service ownership, interfaces, and consumption boundaries visible before product selection.
  • Enables traceability from architecture intent to implementation, operational evidence, and consuming services.

Constraints

  • The resulting SBB must fit the networks ownership model and document the support, lifecycle, and service-management boundary.
  • Security, privacy, logging, evidence, and compliance controls must be explicit enough to assess BIO2-aligned implementation where applicable.
  • Addressing and DNS records must be authoritative, auditable, and aligned with the approved network model.
  • SBBs must support automation-safe APIs for allocation and lifecycle changes.

Service Description

This ABB offers a network naming and addressing service for allocating, resolving, and governing DC 3.0 names and IP resources. It is consumed by solution architects, platform teams, and service owners as the capability contract for selecting and shaping SBBs.

The service description remains implementation-neutral: product selection, hosting pattern, detailed runbooks, and service levels belong in the mapped SBB and related ADRs.

Roadmaps

  • Baseline: confirm scope, service ownership, constraints, and acceptance criteria for DNS, DHCP, and IPAM.
  • MVP: validate the mapped SBB implementation and record the selected support and lifecycle model.
  • Next: add measurable service levels, evidence requirements, and roadmap dependencies once the SBB is selected.

Landing Zones

  • Private cloud and central DC 3.0 landing zone for core infrastructure and platform services.
  • Government cloud or external cloud landing zones only when the SBB documents the required control set, connectivity model, and data classification fit.

Interfaces

  • DNS, DHCP, and IPAM APIs.
  • Zone transfer or delegation interfaces where approved.
  • Automation, DCIM, and network validation integrations.

Dependencies

  • Depends on dc-network-structure for a supporting capability or integration boundary.
  • Depends on datacenter-infrastructure-management for a supporting capability or integration boundary.
  • Implemented by infoblox as currently mapped SBB traceability.
  • Consuming ABB and SBB dependencies must be recorded as links when solution design identifies concrete upstream or downstream use.

EIRA Alignment

Available SBB's

  • infoblox - Infoblox is a candidate solution building block for the translated DC 3.0 ABB model. It remains candidate until the responsible architects confirm service ownership, support model, and acceptance criteria.