# IPv6

IPv6 is the version of the Internet Protocol that uses 128-bit addresses to identify network interfaces and route packets across interconnected networks.

Cloud concept. Updated 2026-10-29. Page: https://blowstack.com/tools/cloud-concepts-hub/ipv6

> IPv6 provides a much larger address space than IPv4 and enables cloud workloads to communicate over IPv6-only or dual-stack networks. Engineers must coordinate addressing, routing, security, and DNS, especially the AAAA records that publish IPv6 addresses and the PTR records used for reverse lookups.

Practice exams covering IPv6: [ANS-C01 AWS Certified Advanced Networking - Specialty](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty), [SAA-C03 AWS Certified Solutions Architect - Associate](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate), [SAP-C03 AWS Certified Solutions Architect - Professional](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional).

## 7 key aspects of IPv6

Reliable IPv6 adoption combines address planning, correct DNS record selection, working network paths, and explicit security controls across both native and translated connections.

1. **128-bit addressing and prefix-based routing**: IPv6 provides a large address space organized through CIDR prefixes. Plan nonoverlapping allocations across cloud accounts and on-premises networks so that routing and future expansion remain manageable.
2. **AAAA-based forward resolution**: AAAA records publish IPv6 addresses; A records publish IPv4 addresses. Publish both for a dual-stack name only when both network paths and application listeners work.
3. **Independent DNS transport**: An AAAA query can travel over IPv4, and an A query can travel over IPv6. Troubleshoot resolver connectivity separately from connectivity to the address returned by DNS.
4. **IPv6 reverse DNS**: PTR records under ip6.arpa map reversed hexadecimal address digits to hostnames. Forward and reverse records require separate administration and do not automatically remain synchronized.
5. **Record-type boundaries**: CNAME records refer to other names, while TXT records carry text rather than address mappings. Provider-specific alias features can publish AAAA answers for supported targets without behaving exactly like conventional CNAME records.
6. **Coexistence and translation**: Dual stack supports native IPv4 and IPv6 communication but requires operating both paths. IPv6-only clients can reach some IPv4-only destinations through coordinated DNS64 and NAT64, not through DNS changes alone.
7. **Explicit security and reachability**: IPv6 needs appropriate routes, filtering rules, and application bindings even when DNS resolves correctly. Validate required ICMPv6 handling and do not treat the absence of NAT as either automatic exposure or sufficient protection.

## Cloud services for IPv6

Amazon VPC supplies the addressing, routes, and security controls that make IPv6 connectivity possible. Elastic Load Balancing can expose an application through an IPv6-capable frontend, while Amazon Route 53 publishes the corresponding AAAA records or aliases. Route 53 Resolver connects cloud and on-premises DNS namespaces through forwarding and supports DNS64 where translation is required. These components must be configured together: correct DNS answers cannot compensate for missing routes, blocked IPv6 traffic, or an IPv4-only listener. Test resolution and application connectivity separately from each relevant account and network.

- **[Amazon Route 53](https://blowstack.com/tools/cloud-services-hub/amazon-route-53)**: Hosts A, AAAA, TXT, and PTR records in public or private hosted zones as appropriate. AAAA alias records can direct queries to supported IPv6-capable AWS targets, including at a zone apex.
- **[Amazon VPC](https://blowstack.com/tools/cloud-services-hub/amazon-vpc)**: Provides IPv6 addressing, subnet routing, and network security controls for cloud workloads. An egress-only internet gateway supports outbound-initiated IPv6 internet communication, while a NAT gateway can provide NAT64 for IPv6 clients reaching IPv4 destinations.

## IPv6 exam questions

Real practice exam questions on IPv6, with the correct answer and its explanation.

### Question 1 (SAA-C03)

**Question:**

A company runs a public HTTPS API behind an IPv4-only Application Load Balancer (ALB). The ALB forwards requests to an IPv4 target group containing EC2 instances in private subnets. A rapidly growing customer fleet will include devices that have only IPv6 connectivity and no access to an IPv4 translation service. Existing IPv4 clients must retain access to the same API hostname.

The company must support both client populations without changing the instances' addressing or the target group. Which solution meets these requirements?

**Correct answer:** Associate IPv6 CIDR blocks with the VPC and the ALB subnets. Configure the ALB for dual-stack addressing, route ::/0 from its subnets to an internet gateway, allow HTTPS over IPv6, and add an AAAA alias record alongside the existing A alias record.

**Explanation:** A dual-stack ALB accepts both IPv4 and IPv6 client connections while continuing to forward requests to an IPv4 target group. IPv6 addressing, internet gateway routes, appropriate security rules, and an AAAA alias record provide the required IPv6 client path without changing the instances.

### Question 2 (SAP-C03)

**Question:**

A company runs a production application in an IPv4-only VPC with six subnets across three Availability Zones. A solutions architect must introduce dual-stack networking in only two existing application subnets in different Availability Zones. The other four subnets must remain IPv4-only during the pilot. All existing IPv4 addresses and subnet IDs must remain unchanged.

The networking team has prepared an IPv6 IPAM pool in the correct AWS Region and granted the application account permission to allocate from it. Company policy requires the VPC's IPv6 address space to come from this pool. Separate deployment stages will configure workload IPv6 addresses, routing, and security rules.

Which address-provisioning plan meets these requirements?

**Correct answer:** Associate an IPAM-allocated /56 IPv6 CIDR block with the VPC. Associate a distinct /64 from that range with each pilot subnet, retaining their IPv4 CIDR blocks. Leave the other subnet CIDR associations unchanged.

**Explanation:** An IPAM-allocated IPv6 CIDR is a supported VPC address source. After associating it with the VPC, the company can associate distinct /64 ranges from it with the two existing pilot subnets. These associations preserve existing IPv4 addressing and subnet IDs and do not require enabling IPv6 in the remaining subnets.

### Question 3 (ANS-C01)

**Question:**

A company manages a Route 53 private hosted zone named services.example.com in a networking account. The zone is associated with a shared-services VPC and application VPCs in several accounts. On-premises DNS servers conditionally forward queries for this namespace to IPv4-only Route 53 Resolver inbound endpoints in the shared-services VPC.

The record inventory.services.example.com currently has an A record for a server's private IPv4 address. The server now also has a fixed IPv6 address. On-premises dual-stack clients can connect successfully to the server by using either address directly. However, an AAAA query for inventory.services.example.com through the on-premises DNS servers returns NOERROR with no answers. There are no conflicting Resolver rules, and the existing forwarding path works correctly.

The company must enable clients to discover the server's native IPv6 address while preserving IPv4 access. The DNS forwarding connection must remain IPv4-only, and no address translation may be introduced. Which change meets these requirements?

**Correct answer:** Add an AAAA record for inventory.services.example.com containing the server's assigned IPv6 address. Retain the A record and the existing IPv4 forwarding configuration.

**Explanation:** The A and AAAA records can coexist at the same hostname to support both address families. DNS queries and responses containing IPv6 addresses can travel over IPv4. The existing inbound endpoints can therefore return the AAAA answer without any change to DNS transport, and client-to-server IPv6 connectivity has already been verified.

## Practice IPv6 in a full exam

Questions on IPv6 in each practice exam, with every answer option and an explanation for each:

- [SAP-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional): 3 questions
- [SAA-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate): 1 question
- [ANS-C01](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty): 1 question

## What is IPv6

IPv6 uses 128-bit addresses, written as hexadecimal groups separated by colons, rather than IPv4's 32-bit dotted-decimal addresses. Leading zeros within a group can be omitted, and one consecutive sequence of all-zero groups can be compressed with a double colon. For example, 2001:db8:10::25 is an IPv6 address from a prefix reserved for documentation. Prefix notation, such as /64, identifies how many leading bits belong to the network prefix. The larger address space supports extensive subnetting and reduces the need for address conservation through network address translation.

For DNS, the central distinction is that an A record maps a name to an IPv4 address, whereas an AAAA record maps a name to an IPv6 address. A dual-stack application can publish both record types for the same hostname. For example, api.example.com might have an A record containing 192.0.2.25 and an AAAA record containing 2001:db8:10::25. Clients select an address using their networking capabilities and connection-selection behavior; many implement Happy Eyeballs to reduce delays when one address family is unusable. Publishing an AAAA record does not make an IPv4-only application or network IPv6-capable.

DNS record types and DNS transport are independent. A client can request and receive an AAAA record through a DNS connection carried over IPv4, or retrieve an A record over IPv6. This distinction matters in hybrid networks: an on-premises resolver can forward an AAAA query to a cloud resolver without requiring the forwarding connection itself to use IPv6. However, the client still needs a working IPv6 path to connect to the returned IPv6 address.

Reverse DNS uses PTR records. IPv6 reverse names are placed under ip6.arpa and represent the fully expanded address as individual hexadecimal digits in reverse order, separated by dots. This differs from IPv4 reverse DNS under in-addr.arpa. Creating a forward AAAA record does not automatically establish the corresponding reverse record. Reverse-zone delegation or a provider-controlled reverse-DNS configuration is needed, and a PTR response alone does not prove the identity or trustworthiness of a host.

Other record types have distinct roles. A CNAME redirects DNS resolution to another hostname, whose records determine the eventual addresses; it does not itself contain an IPv6 address. TXT records carry text such as domain-verification values or email policy data and do not provide IPv6 address resolution. An Amazon Route 53 alias is a provider-specific DNS feature rather than a separate standard DNS record type. For an eligible IPv6-capable target, an AAAA alias can return IPv6 addresses and can be used at the zone apex, where a conventional CNAME is not permitted.

In hybrid and multi-account environments, ensure that private hosted-zone associations, resolver forwarding rules, and reverse-zone ownership produce consistent answers for the intended clients. Avoid forwarding loops and distinguish an authoritative answer containing no AAAA data from an actual resolution failure. DNS64 can synthesize an AAAA answer from an IPv4 A record for an IPv4-only destination when no native AAAA answer exists, but usable connectivity also requires a suitable NAT64 path. DNS64 alone does not translate application traffic.

Operationally, IPv6 requires its own routes, firewall rules, and application listeners. A global IPv6 address does not automatically make a workload reachable from the internet, and eliminating NAT does not eliminate the need for security controls. Permit required ICMPv6 traffic, including Packet Too Big messages used for path MTU discovery. Before publishing AAAA records, test reachability from representative clients, inspect both address families, and account for DNS caching during deployment or rollback. Dual stack improves compatibility but increases the number of network paths that engineers must secure and troubleshoot.

## Learn IPv6 in lessons

2 short lessons on IPv6 in 2 certification courses.

- SAA-C03: IPv6: scaling networks with dual stack (Premium), https://app.blowstack.com/lessons/ipv6-scaling-networks-with-dual-stack-saa-c03
- SAP-C03: IPv6: staged adoption in VPC workloads (Premium), https://app.blowstack.com/lessons/ipv6-staged-adoption-in-vpc-workloads-sap-c03
