Open rvem opened 1 year ago
This issue has been automatically marked as stale because it has been open 30 days with no activity. Remove stale label or comment or this issue will be closed in 10 days
Still relevant
I'm having this issue as well. Use case is creating a publicly reachable machine with only an IPv6 IP.
There are 2 solutions:
64:ff9b::/96
In my case however, I don't need a public IPv4 IP, I do need NAT64.
This issue has been automatically marked as stale because it has been open 30 days with no activity. Remove stale label or comment or this issue will be closed in 10 days
Still relevant
This issue has been automatically marked as stale because it has been open 30 days with no activity. Remove stale label or comment or this issue will be closed in 10 days
Still relevant
Description
public_subnet_enable_dns64
istrue
by default and withenable_ipv6 = true;
this enables DNS64 for created public subnets.However, if a given domain doesn't have an IPv6 record, it's resolved to
64:ff9b::/96
which in turn needs an additional route setup to work correctly.Somewhat similar to #923, but for public subnets.
Versions
Module version [Required]:
5.1.1
Terraform version:
1.5.4
Provider version(s): AWS -
5.10.0
Reproduction Code [Required]
Steps to reproduce the behavior:
curl -6 api.github.com
from the EC2 instance within one of the public subnets above hangs.Expected behavior
DNS64 enabled along with the corresponding route for resolving
64:ff9b::/96
Actual behavior
An IP from
64:ff9b::/96
is not routed correctly:(