Network Address Translation 64 (NAT64), which is typically used to enable communication between IPv6only hosts and IPv4only hosts, can be deployed in a stateful configuration. When configured as stateful, NAT64 maps multiple IPv6 addresses to a single IPv4 address and keeps track of the state of each connection.

Static mappings can also be applied manually. NAT64 can also be deployed in a stateless configuration. When operating in a stateless configuration, NAT64 uses algorithms to create a one-to-one relationship
between IPv6 addresses on the inside network and IPv4 addresses on the outside network. Although this technique preserves endtoend connectivity at the Network layer, it does not conserve IPv4 addresses the way a stateful many-to-one configuration does.

NAT-Protocol Translation (NATPT), not NAT64, uses Domain Name System Application Level Gateway (DNSALG) for name resolution. NATPT is a predecessor of NAT64? it supports bidirectional translation of addresses between IPv6 and IPv4 networks. In NATPT, the DNSALG function is included, along with the address family translation (AFT) function, as part of the protocol. NAT64, on the other hand, is typically deployed alongside an independent Domain Name System (DNS) solution, such as DNS64, to facilitate name resolution.

Network Prefix Translation version 6 (NPTv6), not NAT64, translates unique IPv6 prefixes to other unique IPv6 prefixes. As the name implies, NPTv6 enables the stateless translation of inside IPv6 prefixes to outside IPv6 prefixes at the Internet edge. NPTv6 creates a one-to-one relationship between addresses on each side of the translating device in order to maintain end-to-end reachability at the Network layer. NPTv6 does not modify the interface identifier portion of an IPv6 address.