Allow Custom Domains for Spaces CDN Without Full Domain Management
Eric
Currently, to use a custom domain with DigitalOcean Spaces CDN (e.g., cdn.example.com pointing to my-space.fra1.cdn.digitaloceanspaces.com), I need to transfer my entire domain's DNS management to DigitalOcean nameservers. This is problematic because:
Many users prefer managing DNS with Cloudflare for better performance, DDoS protection, and advanced features
Domain consolidation - users want to keep all domains in one DNS provider
Current workarounds are complex - requiring Workers, redirects, or proxies that break the user experience
Proposed Solution:
Allow custom domain verification through:
DNS TXT record verification (like most CDN providers)
CNAME verification method
File-based verification on the domain
Benefits:
Users can keep their preferred DNS provider
Simpler setup process
Better user experience with branded CDN URLs
Competitive with other CDN providers (Cloudflare, AWS CloudFront, etc.)
This would make DigitalOcean Spaces more competitive and user-friendly for developers who want branded CDN URLs without the complexity of full DNS migration.