DNS64
What is DNS64?
DNS64, defined in RFC 6147, lets an IPv6-only client reach an IPv4-only destination by synthesizing an IPv6 address from the destination's A record when no AAAA record exists, for a paired NAT64 translator to route. AdminKit's IPv6 guide covers how transition techniques like DNS64 change what a home network can reach.
By AdminKit team, Netbase JSC · Updated
DNS64, defined in RFC 6147, is a DNS resolver behavior that lets an IPv6-only client discover IPv4-only destinations through an ordinary AAAA record lookup. When a DNS64 resolver receives a query for a name’s AAAA record and the authoritative answer contains no AAAA record at all, it instead looks up the name’s A record and synthesizes a corresponding IPv6 address by embedding the IPv4 address inside an IPv6 prefix, rather than returning NXDOMAIN or an empty answer the way a plain resolver would. That synthesized address uses either the Well-Known Prefix 64:ff9b::/96 defined in RFC 6052 and listed in IANA’s IPv6 Special-Purpose Address Registry, or a network-specific prefix an operator chooses instead, and it has to match whatever prefix the network’s NAT64 translator expects, since DNS64 only manufactures an address for NAT64 to actually route — the two are designed to be deployed together, and mismatched prefixes between them break the whole path even though each component works correctly on its own. Neither the client nor the destination server needs any IPv6/IPv4 awareness added for this to work; the translation is transparent at both ends. On a resolver, the prefix is a configuration setting: Unbound’s dns64-prefix option sets the prefix used to synthesize AAAA records, must be /96 or shorter, and defaults to 64:ff9b::/96.
DNS64 + NAT64, how the pieces fit:
- DNS64 synthesizes an IPv6 address from an IPv4-only destination’s A record.
- NAT64 does the actual traffic translation for the address DNS64 manufactured.
- Both must agree on the same IPv6 prefix, or the whole path breaks.
DNS64 is part of AdminKit’s DNS cluster; the full AdminKit glossary lists other related terms.
Frequently asked questions
What does DNS64 actually synthesize?
An IPv6 address for a destination that has no AAAA record, built from that destination's A record when a DNS64 resolver gets a AAAA query and the authoritative answer has none at all.
Does DNS64 work on its own, or does it need another component?
It needs a paired NAT64 translator -- DNS64 only manufactures the synthesized IPv6 address, and NAT64 is what actually routes and translates the traffic sent to it; mismatched prefixes between the two break the path even though each works correctly alone.
What prefix does a DNS64-synthesized address use?
Either the Well-Known Prefix 64:ff9b::/96 defined in RFC 6052, or a network-specific prefix an operator chooses instead -- whichever one, it has to match what the network's NAT64 translator expects.
Does the client or the destination server need to know about DNS64?
No -- neither side needs any added IPv6/IPv4 awareness; the translation is transparent at both ends.