IPv6 to IPv4 — how translation works and when you need it.
As networks move to IPv6, not every destination on the internet has caught up. Some services still only support IPv4. Translation technologies bridge the gap — here's how they work, when they're needed, and where things are heading.
Tired of fighting your ISP? HIT Pacific — transparent pricing, no lock-in, real local support.
See our plansWhy this happens
- Not all internet servers have IPv6 addresses yet — the transition from IPv4 is ongoing
- Some legacy software and embedded systems only create IPv4 connections
- A small number of gaming platforms, streaming services, and older VPN systems are IPv4-only
- Translation is a transitional technology — as IPv6 adoption grows, the need for it declines
How to fix it — step by step
-
1. How NAT64 handles IPv6 connections to IPv4-only destinations
NAT64 is a network-side gateway that translates IPv6 connections into IPv4 connections when reaching IPv4-only destinations. When a device on an IPv6 network wants to reach a server that has no IPv6 address, the NAT64 gateway handles the translation. The device and the user don't need to do anything — it's invisible.
-
2. How DNS64 creates synthetic routes through the NAT64 gateway
DNS64 works alongside NAT64. When you look up a domain that has no AAAA (IPv6) record, DNS64 synthesises one that points through the NAT64 gateway. Your device connects via IPv6 to the gateway, which connects via IPv4 to the real destination. The whole process is transparent to the application.
-
3. How 464XLAT lets IPv4-only apps run on an IPv6-only connection
464XLAT handles IPv4-literal applications — software that creates IPv4 sockets directly rather than using a hostname lookup. It adds a CLAT (client-side translator) component that creates a virtual IPv4 interface on the device, letting IPv4-only apps run on an IPv6-only connection. All major mobile operating systems support 464XLAT natively — your phone likely uses it already on mobile data.
-
4. What this means in practice
On a well-configured IPv6-primary network with NAT64/DNS64 and 464XLAT, the vast majority of internet activity — including reaching IPv4-only destinations — works without any user awareness. The translation happens in the background. HIT Pacific has 464XLAT on the network infrastructure roadmap.
-
5. What you don't need
Tunneling services, 6to4 gateways, and Teredo are legacy workarounds invented when ISPs didn't provide native IPv6. They wrap IPv6 packets inside IPv4 to reach a remote tunnel endpoint, adding latency and a dependency on a third-party service. Native IPv6 with NAT64 and 464XLAT is always preferable to any tunnel.
Still having trouble?
If none of these steps resolve the problem, it may be an issue with your current provider. HIT Pacific offers transparent pricing, faster fault response, and local support.
See our plans