DNS64
Publication date: June 23, 2022 (Diagram history)
This architecture shows how DNS64 enables DNS resolution for queries from IPv6-only resources to IPv4-only names by synthesizing IPv6 addresses from IPv4 addresses using the well-known 64:ff9b::/96 prefix.
DNS64 architecture
The following numbered items describe the key components in this architecture:
When you create a Amazon VPC, the Amazon Route 53 Resolver that is created by default maps to a DNS server that runs on a reserved IPv4 address for the Amazon VPC network range, plus 2. For the IPv6 stack, the Route 53 Resolver can be reached at the local address fd00:ec2::253.
Without DNS64, a DNS query for an IPv4-only service will yield an IPv4 destination address in response and your IPv6-only service cannot communicate with it. To bridge this communication gap, you can enable DNS64 for a subnet and it applies to all the AWS resources within that subnet.
The IPv6-only instance sends a DNS query for an IPv4-only endpoint to the Route 53 Resolver.
With DNS64, the Route 53 Resolver looks up the DNS record for the service you queried for. If the record contains an IPv6 address, it returns the original record and the connection is established without any translation over IPv6. If there is no IPv6 address associated with the destination in the DNS record, the Route 53 Resolver synthesizes one by prepending the well-known /96 prefix, defined in RFC6052 (64:ff9b::/96), to the IPv4 address in the record.
The Amazon Route 53 Resolver replies with a synthesized IPv6 address made of the well-known 64:ff9b::/96 prefix and the IPv4 address.
Further reading
For additional information, see the following resources:
Diagram history
To be notified about updates to this reference architecture diagram, subscribe to the RSS feed.
| Change | Description | Date |
|---|---|---|
Reference architecture diagram first published. | June 23, 2022 | |
Reference architecture diagram first published. | June 23, 2022 | |
Reference architecture diagram first published. | June 23, 2022 | |
Reference architecture diagram first published. | June 23, 2022 | |
Reference architecture diagram first published. | June 23, 2022 | |
Reference architecture diagram first published. | June 23, 2022 | |
Reference architecture diagram first published. | June 23, 2022 | |
Reference architecture diagram first published. | June 23, 2022 | |
Initial publication | Reference architecture diagram first published. | June 23, 2022 |
Reference architecture diagram first published. | June 23, 2022 | |
Reference architecture diagram first published. | June 23, 2022 | |
Reference architecture diagram first published. | June 23, 2022 | |
Reference architecture diagram first published. | June 23, 2022 | |
Reference architecture diagram first published. | June 23, 2022 | |
Reference architecture diagram first published. | June 23, 2022 | |
Reference architecture diagram first published. | June 23, 2022 | |
Reference architecture diagram first published. | June 23, 2022 |
Note
To subscribe to RSS updates, you must have an RSS plugin enabled for the browser you are using.
