IPv4 vs IPv6 for Business Networks and Hosted Services
IPv6 expands internet addressing but does not simply replace every IPv4 dependency overnight. Learn how businesses can plan dual-stack adoption safely.
IPv4 and IPv6 are internet protocols used to address and route network traffic. IPv4 remains widely used but has limited address space. IPv6 provides a much larger address space and different operational conventions. Many businesses run both during a controlled transition.
Address space and NAT
IPv4 scarcity led to extensive network address translation. IPv6 can assign globally unique addresses without relying on NAT for address conservation. That does not mean devices should be exposed: firewall policy remains essential.
Dual stack
A dual-stack network supports IPv4 and IPv6 together, allowing compatible applications to use IPv6 while retaining IPv4 reachability. It adds operational work because monitoring, DNS, firewall rules and troubleshooting must cover both protocols.
DNS and hosted services
IPv4 services commonly use A records and IPv6 uses AAAA records. Publish IPv6 only when the complete service path works, including firewall, load balancer and application. A broken IPv6 path can create intermittent user problems.
Security and monitoring
Apply equivalent policy to both protocols and avoid ignoring IPv6 because it was not intentionally deployed. Inventory router advertisements, address assignment and tunnels. Ensure vulnerability scanning and logs understand IPv6 notation.
Provider and application support
Confirm that connectivity, IP transit, hosting, VPNs and third-party allowlists support the required protocol. Legacy equipment may need replacement or an explicit translation design.
A controlled adoption plan
- Inventory addresses, applications and dependencies.
- Obtain a suitable addressing and routing plan.
- Update firewalls, DNS and monitoring.
- Pilot with representative services.
- Test failure and IPv4-only counterparties.
See how our managed network supports business routing. Ask our team to review your IPv4 and IPv6 dependencies.
Pilot example
Begin with a non-critical public service and a controlled user network. Publish the correct DNS record, apply explicit firewall policy and monitor both successful and failed IPv6 connections. Test from several external networks because one provider path is not representative.
If the pilot fails, remove or correct the IPv6 advertisement rather than leaving a partial service. Record lessons for address assignment, logging and support before extending dual stack to more sites or customer-facing applications.
