- Newest
- Most votes
- Most comments
I think this the document you are looking for
https://repost.aws/knowledge-center/locate-cloudfront-distribution-owner-account
So you would create your distribution without CNAMEs and then check which account has the conflicting distribution. If the account is not one of your, you would need to contact AWS support to resolve the issue.
Embarrassed to say that the conflict was another cloudfront distribution in the same account. It hadn't shown up in the Resource Explorer, so I didn't think it was still there, but I happened to check the CloudFront console and found it.
Hi jric
You can use a CNAME lookup tool such as MxToolbox (https://mxtoolbox.com/CNAMELookup.aspx) or use the dig command (dig <domain>) to figure out what resource is attached to this particular domain.
Depending on the result you can remove the relevant records from the corresponding resource.
I had tried that, but I don't think it's helping? It says "DNS Record not found". It also says, "Your DNS hosting provider is "Amazon Route 53"". It also says, "Reported by ns-153.awsdns-19.com on 7/29/2023 at 2:58:05 PM (UTC -5)".
Hi jric
I think Kallu's answer will provide you with a better path forward to figure out this issue. Simply create the Cloudfront distribution without an alias then run the ListConflictingAliases command which will point you to the exact conflicting record.
Relevant content
- Accepted Answerasked a month ago
- CloudFront - One or more of the CNAMEs you provided are already associated with a different resourceAccepted Answerasked 5 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 9 months ago
Good to hear you found it. If you think some of the answers helped in process you can accept multiple answers ;-)