NAT64
What is NAT64?
NAT64, defined in RFC 6146, is a stateful mechanism that lets an IPv6-only client reach an IPv4-only server by translating packets at a network boundary, usually paired with DNS64 for address synthesis. AdminKit's CGNAT guide compares NAT64 with the IPv4-side address-sharing technique it's often confused with.
By AdminKit team, Netbase JSC · Updated
NAT64, defined in RFC 6146 (a Proposed Standard per its IETF Datatracker entry), is a stateful translation mechanism that lets an IPv6-only client reach an IPv4-only server without either side running dual stack networking. A NAT64 device sits at the boundary between an IPv6-only network and the IPv4 internet: when an IPv6 client sends a packet addressed to a synthesized IPv6 address representing an IPv4 destination, the NAT64 device rewrites the packet into IPv4, tracks the resulting connection state, and translates the IPv4 server’s replies back into IPv6 for the client. Because many IPv6-only clients typically share a limited pool of public IPv4 addresses on the far side, NAT64 usually also performs port translation, the same way ordinary IPv4-to-IPv4 NAT does. NAT64 only works for connections an IPv6 client initiates; an IPv4-only host on the internet cannot start a connection to a client behind it. NAT64 is normally deployed together with DNS64, defined in RFC 6147, which synthesizes the IPv6 addresses NAT64 needs by rewriting a destination’s DNS answer — without DNS64, a client would have no IPv6 address to send its IPv4-bound traffic to in the first place. Google Public DNS64 runs exactly this pairing as a real service, synthesizing AAAA records for IPv4-only destinations so IPv6-only networks can reach them through a NAT64 gateway. Apple’s guidance on supporting IPv6-only networks relies on the same pairing from the app side, telling developers that a server on the wider internet “will be accessible to IPv6-only devices via DNS64/NAT64” even before it supports IPv6 itself. Mobile networks commonly pair this NAT64/DNS64 setup with 464XLAT, which adds a device-side translator so apps that hardcode an IPv4 address or skip DNS entirely still reach the IPv4 internet.
NAT64 is part of AdminKit’s IP & network cluster; the full AdminKit glossary lists other related terms.
Frequently asked questions
Can an IPv4-only host on the internet start a connection to a client behind NAT64?
No -- NAT64 only works for connections the IPv6-only client initiates; an IPv4-only host can't start a connection to a client behind it, the same directionality ordinary NAT enforces.
Why does NAT64 usually also do port translation?
Because many IPv6-only clients typically share a limited pool of public IPv4 addresses on the far side, so NAT64 performs port translation the same way ordinary IPv4-to-IPv4 NAT does to tell shared connections apart.
What does NAT64 depend on to get an IPv6 address to translate in the first place?
DNS64, defined in RFC 6147 -- it synthesizes the IPv6 addresses NAT64 needs by rewriting a destination's DNS answer; without it, a client would have no IPv6 address to send its IPv4-bound traffic to at all.
How does 464XLAT relate to NAT64?
Mobile networks commonly pair NAT64/DNS64 with 464XLAT, which adds a device-side translator so apps that hardcode an IPv4 address or skip DNS entirely still reach the IPv4 internet.
Sources
- RFC 6146 -- Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers
- RFC 6147 -- DNS64: DNS Extensions for Network Address Translation from IPv6 Clients to IPv4 Servers
- IETF Datatracker -- RFC 6146 document status
- Google -- Google Public DNS64
- Apple Developer — Supporting IPv6-only Networks