Allow custom DNS hostnames to be added to cluster config / TLS certs
Since Atlas clusters now support different sets of hostnames, it would be good to explore the feasibility of allowing users to add their own hostnames to the cluster configuration and TLS certificates such that custom connection strings can be used.
One use case for this is being able to "wrap" Atlas connection strings, such that an application's connection string would never need to change despite underlying cluster changes (cluster being moved between projects, etc.)
This could also be useful if you wished to whitelabel your cluster.
Another usecase for this is we can use the custom hostname/s in the mongodb connection string in the application instead of renaming the cluster name which is not possible as of now.
We prefer to be able to set hostnames that our within our private domain to meet our services' naming convention.
Our use case for this feature is as follows:
We have many small clusters, each cluster is associated with a service which has multiple environments (dev/test/prod).
It's much simpler for us to spin-up clusters and then add custom DNS records for those clusters that fit a set pattern, e.g: mongodb.<service-namespace>.<environment>.<company>.<tld> and have this connection address used across all our clients than it is to reconfigure every single client with custom DNS information across all environments after a new mongodb cluster is created or changed.
Because we are currently have to use the real atlas DNS, it creates a hard dependency between infrastructure and application configuration layers which would ideally be avoided.