Talk to a specialist

BLOG VLSM.io

IPv6: a solution to IPv4 exhaustion

IPv6 expands address space and enables growth planning at a different scale. Its benefits emerge when networks, applications, and destinations evolve together.

IPv6-only egressConnectivity and intelligence
Globe with IPv6-only outbound connections
IPv6-only egress2001:db8::24Illustrative addresses
Estimated reading time: 7 min8 sections
IPv6: a solution to IPv4 exhaustion
IPv6: a solution to IPv4 exhaustion
01

An addressing foundation for growth

IPv6 provides a 128-bit address space, much larger than the 32-bit space of IPv4. This difference allows network planning without continually competing for small address pools. Its business value is not found in reciting an enormous number of combinations. It lies in organizing branches, environments, and services through a consistent hierarchy. A project can reserve room for expansion and separate functions without making the conservation of every individual address the dominant consideration behind every infrastructure decision.

Address scarcity is addressed through architectural evolution, rather than automatic conversion of existing resources. A new IPv6 prefix does not enlarge an old IPv4 block or transform a destination reachable only through IPv4. They belong to different protocol families. An organization benefits by using IPv6 on compatible paths while retaining an explicit strategy for remaining dependencies. This allows progress without promising an immediate replacement of every device, application, and partner involved in operating a production service or completing a customer workflow.

CONNECTIONS IN MOTIONThe path of your connection
ApplicationJob or integration
ConnectivityIPv6-only egress
DestinationSystem or service
The illustrated service uses IPv6-only Internet egress. IPv4 egress requires a separate service. The animation does not represent live traffic.
02

Plan networks around function, location, and growth

An IPv6 plan should start with organizational structure. Separate locations, production environments, staging, management, and shared services. Reserve coherent ranges for each role and leave room for additional sites. Prefix selection must consider the received delegation, deployed technologies, and administrative responsibility. Avoid mechanically copying IPv4 masks into the new plan: local networking and autoconfiguration patterns need their own treatment. A structure that is easy to document and audit can be more valuable than a tightly packed division that becomes difficult to operate.

For example, a company with several sites can establish a stable convention identifying location and purpose, supported by a central inventory. The convention does not need to encode every business detail in an address; frequently changing information belongs in records. The objective is aggregation and avoidance of overlap while preserving flexibility. When obtaining subnets, confirm the delegated quantity and delivery method. Available commercial prefixes should not be interpreted as universal recommendations for every network or as automatic authorization for global route announcements.

03

The complete path must support IPv6

IPv6 availability on the access link is only one necessary condition. An application depends on name resolution, address selection, routing, security policies, and the destination service. A web workflow may additionally involve identity services, file storage, and external APIs. Map these dependencies before removing IPv4 compatibility. A test that opens a homepage confirms only a limited part of the experience; the useful outcome is completing the task that a person or automation actually needs to perform in the deployed environment.

Build a workflow matrix containing destinations, the observed address family, and the outcome of each step. Include incoming and outgoing connections when callbacks or bidirectional integrations are involved. Test from the runtime intended for production because a workstation may have different connectivity from a server or container. Preserve timestamps and configuration evidence without exposing credentials. This creates a known baseline for future failures, rather than relying on memories of an informal test performed from another machine with a different network path.

TRAFFIC AND ADDRESSINGOne IPv6 service. IPv6-only egress.
Source2001:db8::24
Destination2001:db8::20
Return2001:db8::24
The outbound path of this service uses IPv6 only. Reaching an IPv4 destination requires a separate IPv4 service; there is no dual-stack egress. Illustrative addresses.
04

Retain a strategy for IPv4 destinations

During transition, some paths will continue to depend on IPv4. A deployment supporting both families can address that need if both are operated and monitored. Other projects use specific translation mechanisms or proxies that establish destination-appropriate outbound connections. The choice depends on the application and control over infrastructure. Naming a technology is insufficient: describe where each connection terminates, which family is used on every segment, and how the system reacts when the preferred path is unavailable during normal operation.

In a proxy-based automation, the client-to-proxy connection can use one family while outbound connectivity uses another, depending on implementation. This does not mean that an IPv4 packet became native IPv6 merely because a URL setting changed. Intermediate connections and functions need observation. Validate DNS resolution, egress source, authentication, and application protocol support. Documentation should make these choices visible so the team understands which IPv4 dependencies remain even after part of the infrastructure has been modernized and assigned IPv6 addresses.

05

Evolution requires equivalent controls

A larger address space does not automatically secure a service. Define access, segmentation, and monitoring policies for IPv6 with the same care applied to the existing environment. A rule maintained only for IPv4 may leave an IPv6 path behaving differently. Review inventory, event collection, and incident response tools as well. Teams must identify a source, connect it to the responsible service, and understand changes over time, even when addresses appear in different textual forms across logs, dashboards, and configuration interfaces.

Security tests should confirm expected outcomes rather than merely copy configuration files. A restricted service must remain restricted across both families, while a public service should respond according to the approved design. Check administrative access, internal dependencies, and exposure through load balancers. At the same time, avoid indiscriminately blocking essential protocol functions to reproduce habits from another architecture. Use rules reviewed for the environment and observe their effects. The desired balance combines working availability with an access surface deliberately defined by the organization.

06

Migrate by service with acceptance criteria

Choose an initial service with available owners and understood dependencies. Define success: completed transactions, latency within target, no regressions, and monitoring evidence. Run load tests consistent with authorized operations and observe relevant usage periods before expanding the change. This process produces reusable knowledge about DNS, deployment, and support. A pilot without objective criteria may appear successful even when some users silently rely on an alternative IPv4 path. Measure the family actually used rather than inferring it from the intended configuration.

Prepare rollback as well. Record changes, conditions for stopping expansion, and the procedure for restoring previous behavior. A planned reversal is not a failure; it reduces the impact of an unidentified dependency. After stabilizing the service, update procedures and training. IPv6 becomes an ordinary operational capability when new deliveries include requirements, testing, and monitoring for that family from the start. At that point, continued evolution no longer depends entirely on an isolated migration project or on the knowledge of one specialist.

FROM CONNECTION TO RESULTTurn requirements into an observable operation.
Plan
Connect
Monitor
Destination planning, connectivity configuration, and result validation are complementary steps. The animation represents this workflow.
07

Measure benefits through capacity and continuity

Evaluate results using service-related indicators: workflows completed over IPv6, remaining IPv4 dependencies, incidents by family, and the time needed to provision new networks. Avoid treating an isolated percentage as proof of maturity. High traffic volume can coexist with an incompatible critical integration. Conversely, a small operation may have excellent functional coverage. The indicator set should reveal whether the architecture became more predictable and whether growth now requires less improvisation in addressing management, operational support, and coordination between application and network teams.

When discussing a project with VLSM.io, present the current environment and priority destinations to define delivery consistent with that plan. A project can use separately contracted IPv4 and IPv6 services as required. Each retains its own Internet egress family exclusively, without dual-stack delivery.

Decisions should clearly distinguish what has been validated from what still requires testing. IPv6 provides a strong foundation for overcoming addressing limitations; realizing that opportunity requires design, deployment, and follow-up aligned with actual application behavior rather than an assumption that a larger address pool solves every dependency.

08

Institutional references

Reference documents on the topics covered in this article.