Custom domains: Support for actual CNAME records#328

Your current setup for custom domains doesn’t actually use CNAME records but requires a reverse-proxy that handles HTTPS.

Not everyone uses or wants to use a cloud-based reverse-proxy like Cloudflare. So it would be awesome to have the following:

• Custom domains should actually use CNAME records. This will ensure that requests to custom domains go directly to your server.
• Your server should then handle HTTPS via domain validation. With Let’s Encrypt or similar providers this can be automated and is also free (apart from initial setup).

The big advantage is that your users don’t have to setup HTTPS manually. It will just work™.