Topic starter
23/06/2026 7:10 pm
TL;DR: IP addresses still underpin routing, DNS resolution, and device identification, but the article shows that IPv4 exhaustion, dual-stack complexity, and IPv6 adoption gaps are now shaping operational risk for network and security teams, according to DigiCert. The bigger lesson is that addressing is no longer just a networking concern; it is a governance problem for connected identity at scale.
Editorial analysis by NHI Mgmt Group, based on content published by DigiCert: “What is an IP Address”.
By the numbers:
- IPv6 uses a 128-bit address structure, enabling an almost limitless pool of addresses, approximately 340 undecillion.
- Google data shows IPv6 global adoption reached just under 50% as of early 2025.
Key questions
Q: How should teams manage IP address changes in dual-stack environments?
A: Treat IPv4 and IPv6 as one governance problem, not two separate tasks.
Q: Why do IPv4 shortages create operational risk for DNS and routing teams?
A: Because scarcity pushes organisations toward NAT, reclaimed space, transfers, and shared address use, which increases dependency density and makes mistakes harder to isolate.
Q: What are the signs that IP address management is too manual?
A: Frequent resolution failures, duplicate assignments, unclear ownership of public and private ranges, and repeated troubleshooting across IPv4 and IPv6 usually indicate weak governance.
Practitioner guidance
- Govern IPv4 as a finite asset Track allocation, reclaim, transfer, and reuse so scarce IPv4 space is managed as an inventory with ownership and lifecycle visibility.
- Audit dual-stack dependencies Map which services require A records, AAAA records, NAT64, or IPv4-only reachability so you can spot hidden protocol dependencies before changes go live.
- Standardise DNS change validation Test resolution, routing, and application reachability on both protocol families before approving configuration changes in production.
Bottom line: IP addresses are still foundational to routing and DNS, but scarcity and mixed-protocol operations make them a governance problem as much as a networking one.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
25/06/2026 3:02 am
Static network identity is no longer a defensible assumption. IP addresses have traditionally been treated as stable identifiers for routing and access decisions, but that assumption weakens as DHCP, NAT, reclaimed IPv4, and dual-stack environments become the norm. The practical consequence is that teams can no longer rely on address permanence as a proxy for trust, ownership, or reachability. Governance now has to account for address volatility as a first-class condition.
A question worth separating out:
Q: How do organisations reduce the risk of IPv4 and IPv6 mismatch?
A: Keep authoritative inventory, enforce change review for DNS and routing updates, and monitor whether all critical services are reachable across the protocol combinations you actually support. Mixed-stack environments fail when teams assume every client and provider sees the same address path.
👉 Read our full editorial: IP address management exposes the limits of static network identity