使用AWS re:Post即您表示您同意 AWS re:Post 使用条款

Mapping Apex address to cloudfront OR S3

0

Hi,
I have posted my issue on another thread on Route 53 forum because initially, I thought that's where the problem is. See https://forums.aws.amazon.com/thread.jspa?threadID=318265&tstart=0

TLDR;
Can we either

  1. Map the LightSail's Apex address to CloudFront instance?, OR
  2. Map the LightSail's Apex address to an S3 instance (This is an attempt to redirect homs.com.my to https://www.homs.com.my), OR
  3. Create a Hosted DNS in Route 53 that maps to the one in Lightsail (So that we actually have 1 hosted zone, not 2)

I inherited this project from my colleague. Initially, we want the domain https://homs.com.my to point to a CloudFront distribution, but of course, we can only map the Apex address only to a static IP.

So, my colleague created another Hosted Zone in Route 53. Now, this is just my guess, but I think he copied the NS from the LightSail DNS zones into the 53 Hosted Zones. And after that is just configuring the A, AAAA and CNAME Records.

When I double-check the NS names with the Domain Registrar in exabytes (I need to go through my client as he won't give me access), the names match so I thought everything should be fine. 2 days later, the domain https://homs.com.my is still down so I reached out to the R53 team for help.

They came back to me and told me I actually have 2 Hosted Zones. So I think, the first zone is the one in LightSail and is currently working, and the second zone is the one my colleague created in R53.

Their suggestion on how to fix this is to copy the configuration in R53, and add them to the older zone in LightSail. Is that doable? Can we map the Apex address to a CloudFront or to an S3 bucket? Or can we configure the R53 zone to map to the one in LightSail?

Thanks

已提问 5 年前408 查看次数
1 回答
0

I should have closed this earlier, but I think I found a workaround to solve this issue. Thanks

已回答 4 年前

您未登录。 登录 发布回答。

一个好的回答可以清楚地解答问题和提供建设性反馈,并能促进提问者的职业发展。

回答问题的准则