DNS/DHCP Consolidation After head2 Decommissioning
head2 Decommissioning Impact Assessment
With head2 decommissioned from the lab.franklin topology, its DNS A/AAAA records and associated DHCP reservations required cleanup across all authoritative zones. Failure to remove these entries had been causing intermittent resolution failures for services that previously depended on head2's IP space (10.10.8.x / 10.10.9.x subnets).
Core BIND9 Zone Cleanup
The primary BIND9 zones (lab.bitsmasher.net, reverse.lab.bitsmasher.net) were audited and purged of all head2-related records:
- Removed 14 A/AAAA record pairs from the forward zone file.
- Removed 8 PTR entries from the reverse zone file for the
10.10.8.xand10.10.9.xranges. - Reloaded zones with
rndc reloadon skynet (the primary DNS authority at 10.10.16.10).
DHCP Reservation Alignment
The DHCP server configuration was updated to eliminate orphaned reservations that pointed to head2's MAC address (decommissioned from the switch port inventory). Remaining active reservations across the lab subnets were validated against the current host inventory:
- labbitsmasher.net: Primary scope — 10.10.8.0/21, reserved range updated.
- research.lab: Secondary scope — 10.10.13.0/24, no orphaned entries found.
- edge.local: Tertiary scope — 172.16.0.0/16, Jetson nodes retained static leases.
Post-cleanup validation confirmed zero stale reservations and full resolution coverage for all remaining active hosts. The IP space formerly assigned to head2 (10.10.8.0–10.10.9.255) is now marked available in the DHCP address pool for future reallocation.