Feature Request

Cloudinary permits to custom the CDN but next-cloudinary, especially, CldImage, doesn't give access to this.

See your own documentation:
https://cloudinary.com/documentation/cloudinary_sdks#cross_sdk_info
https://cloudinary.com/documentation/advanced_url_delivery_options#private_cdns_and_cnames
https://support.cloudinary.com/hc/en-us/articles/202520562-Can-we-deliver-our-assets-using-a-subdomain-of-our-own-domain-like-cdn-example-com

Potential Solution

As for the configuration of the cloudName NEXT_PUBLIC_CLOUDINARY_CLOUD_NAME="<Your Cloud Name>" in .env file. It would be very much appreciated to have the same way to configure a custom CDN. For example:
NEXT_PUBLIC_CLOUDINARY_CNAME="<Your CNAME>"

Or to have a way to pass the CNAME directly to CldImage component.

Thanks