-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Route53 A/AAAA Alias Record to ELB does not use "dualstack" prefix #6271
Comments
@httpdigest is it just the |
I think the documentation is pretty clear about "dualstack" being a simple prefix to the DNS name of the ELB, as per the example:
|
okay, i was thinking it could be anywhere in the value based on the phrasing of
|
Is this issue being addressed? I can successfully create a DNS recordset (alias) to a LB, but the value doesn't include the 'dualstack.' prefix. Manually adding the prefix fixed the recordset. Is there a workaround I can use while waiting for the framework to be fixed? |
…addresses (#8747) **[ISSUE]** Route53 A/AAAA Alias Record created by CDK didn't add prefix 'dualstack' to the dnsName of ElasticLoadBalancer as suggested in [documentation](https://aws.amazon.com/de/premiumsupport/knowledge-center/alias-resource-record-set-route53-cli/), resulting in inability to resolve IPv6 records (outcome consistent with these [docs](https://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-internet-facing-load-balancers.html)). **[APPROACH]** Joined prefix: _dualstack_ to DNS of ELB targets to resolve IPv6 records. Example: > If ELB DNS name is `ALB-xxxxxxxx.us-west-2.elb.amazonaws.com`, > Route53 A/AAAA Alias Record will create Alias Target `dualstack.ALB-xxxxxxxx.us-west-2.elb.amazonaws.com` **[NOTE]** Ignoring the case of using `ApiGatewayDomain(domainName)` because the prefix of 'dualstack' should be added in the `domainName` parameter. ``` new route53.ARecord(this, 'AliasRecord', { zone, target: route53.RecordTarget.fromAlias(new alias.ApiGatewayDomain(domainName)), }); ``` If creating an ApiGatewayDomain for ELB, endpoint for ELB with prefix 'dualstack' should be declared there, not within route53 package. Fixes #6271 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
When creating an ALIAS A/AAAA record in Route53 pointing to an ELB on the Web Console, the name will always have a "dualstack" prefix, as also suggested by the AWS documentation: https://aws.amazon.com/de/premiumsupport/knowledge-center/alias-resource-record-set-route53-cli/
This ensures that both IPv4 and IPv6 addresses are solved.
However, a CDK ARecord as well as a AaaaRecord with a LoadBalancerTarget will not add this "dualstack" prefix.
Reproduction Steps
When looking at Route53 record in the the Web Console, the record will not have the "dualstack" prefix.
Environment
This is 🐛 Bug Report
The text was updated successfully, but these errors were encountered: