Can we have our own CNAME to our own domain? Like cdn.example.com?

A personalized CNAME per domain is a feature available for the "Advanced" plans and above, and requires a quick manual setup on our side.

In order to commence the setup process, proceed to the Settings page and follow the link which will submit a support request to set up a CNAME for your account. 

UPDATE:

Cloudinary supports CNAME for non-secure HTTP traffic, while with HTTPS you will get a private CNAME in the Cloudinary domain, like https://mydomain-res.cloudinary.com (instead of the generic https://res.cloudinary.com).

Cloudinary also supports adding custom CNAMEs for HTTPS traffic, but it's at an extra cost. Contact us for more information.

Have more questions? Submit a request

Comments

  • Avatar
    Richard Latman

    It would be nice if you provided instructions on how to request this.

  • Avatar
    Orly Bogler

    Hi Richard, 

    Thank you for your comment. 

    In order to commence the setup process, available for "Advanced' plans and above, proceed to the  Settings page and follow the link which will submit a support request to set up a CNAME for your account. 

    Please don't hesitate to turn to us for assistance. 

    Thanks

  • Avatar
    Eric Chapman

    Isn't there some SEO issues caused by not having a CNAME? I'm trying to figure out if I should use the service or not.

  • Avatar
    Tobias Marx

    Of course there is. It is not advisable to host your content on a third party domain.

     

    I do not understand why this is not part of any package - but only the advanced plan.

  • Avatar
    Itai Lahan

    Delivering your images via a CDN using the CDN's domain is a very common practice today. Sift through a few popular websites and you'll notice that very few deliver the images from their own domain. Modern search engines correctly take that into account.

  • Avatar
    igdb

    This is potentially a dealbreaker for us. I'm surprised this is how it works, I totally expected CNAMEs to be available for ALL paid plans.

    It keeps all requests tied to a single domains so that there are no questions about legitimacy.

    We have already had a user report that he sees no images on the site because the cloudinary domain has been blacklisted by their firewall company. Think about that, if any other customer of cloudinary was to upload an offensive or illegal image, an entire country could be blocked from viewing resources on our website. This is unacceptable and must be acknowledged and addressed by the cloudinary team.

  • Avatar
    Seshan Bavan

    Hi Guys


    igdb has a valid point I think you need to make the custom CNAME option available for all paid plans. Because some places will block your domain name.

    Thanks

  • Avatar
    Raphael Arias

    igdb +1

  • Avatar
    yumyo

    could not agree more +1

  • Avatar
    Estra SpA

    igdb +1

  • Avatar
    Stephen Johnston

    The SEO impact of this should be minimal at least for Google. Google will see a subdomain, even of your primary domain, as "another site" anyway.

Powered by Zendesk