An error occurred while saving the commentRob commented
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.Rob supported this idea ·