2 Answers
- Newest
- Most votes
- Most comments
1
I also ran into this and a "cleaner" option seems to be with using delegating responsibility for a subdomain to a hosted zone
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/dns-routing-traffic-for-subdomains.html
answered 3 years ago
0
I have come up with a solution. It seems that the record set in Account B does not work and requests the address to hosted zone in Account A so creating the record set in Account A and using the CNAME of the distribution in Account B is the solution. The request goes to the record set in Account A and then it routes to the distribution in Account B.
The below link has the diagram presents the solution:
https://i.stack.imgur.com/1e8Pv.png
answered 5 years ago
Relevant content
- Accepted Answerasked a year ago
- Accepted Answerasked 6 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated a year ago