Articles on: MamuteCloud

Resolving CNAME Conflict Errors

What is this error?


The error "CNAME Already in Use" occurs when you try to add a custom hostname (e.g., app.mysite.com) to your MamuteCloud CDN distribution, but this hostname is already linked to another CloudFront distribution.


Important: AWS CloudFront only allows each hostname to be linked to one distribution at a time. This is a platform limitation, not a MamuteCloud restriction.



Why does this happen?


Common scenarios:


  • Previous CDN setup: You used this domain with another CDN provider or AWS account
  • Migration incomplete: You're migrating from another service but didn't remove the old configuration
  • Testing/staging: The domain was used in a test environment and wasn't cleaned up
  • Duplicate configuration: The hostname exists in multiple distributions (yours or someone else's)



How to resolve


Step 1: Access AWS CloudFront Console


  1. Log into your AWS account at console.aws.amazon.com/cloudfront
  2. Make sure you're in the correct AWS region


Don't have access? If this hostname was configured by a previous provider or team member, you may need to contact them for access.


Step 2: Find the distribution using your hostname


  1. In the CloudFront console, click on each distribution
  2. Look for your hostname (app.mysite.com) in the "Alternate Domain Names (CNAMEs)" section
  3. Note the Distribution ID where it appears


Tip: Use your browser's search function (Ctrl+F / Cmd+F) to search for your domain across distributions.



Step 3: Remove the CNAME from the conflicting distribution


  1. Click on the distribution that contains your hostname
  2. Click the "Edit" button in the "General" tab
  3. In "Alternate Domain Names" section, remove your hostname from the list
  4. Click "Save Changes"


⚠️ Warning: This will break any active configuration using this hostname in that distribution. Make sure this is the correct action before proceeding.




Step 4: Retry in MamuteCloud (immediately available)


Good news: The hostname is released immediately after removal from CloudFront. No waiting needed!


  1. Return to your MamuteCloud dashboard
  2. Click "Retry Adding Domain" in the error modal
  3. The hostname should now link successfully ✅



Still having issues?


Option 1: Domain in another AWS account


If the hostname is in an AWS account you don't control:


  • You own the domain: Update DNS to point to MamuteCloud, then wait 24-48h for CloudFront to release it
  • You don't own the domain: You cannot use this hostname - contact the domain owner


Option 2: Can't find the distribution


If you can't locate where the hostname is configured:


  1. Try searching in all AWS regions (CloudFront is global but some settings are regional)
  2. Check if you have multiple AWS accounts
  3. Contact your previous CDN provider to release the configuration


Option 3: Technical support needed


If you've tried everything and still see the error:


  • Contact MamuteCloud Support via chat (bottom-right corner)
  • Provide: Your hostname, AWS account ID (if applicable), and steps you've already tried



Prevention tips


When migrating from another CDN or AWS account:


✅ Before adding to MamuteCloud:

  1. Remove hostnames from old distributions
  2. Immediately add to MamuteCloud (no waiting needed)


This prevents conflicts and ensures smooth migration.




Updated on: 20/02/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!