When a customer wants to use their private LDAP server in Atlas, they currently need to either expose their name via public DNS or use an internal CA and an IP address. For some customers these scenarios are suboptimal since they want to keep their infrastructure details private, even at DNS layer. The proposed solution is to use the Conditional DNS forwarders in all cloud providers supported by Atlas, so the requests to resolve a private DNS zone (specified by the customer) will be forwarded to the listed DNS servers across the VPC peering connection while all other (public) DNS requests will still be served by the Atlas DNS server. https://cloud.google.com/dns/docs/overview#dns-peering https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resolver-forwarding-outbound-queries.html https://docs.microsoft.com/en-us/azure/virtual-network/virtual-networks-name-resolution-for-vms-and-role-instances#name-resolution-that-uses-your-own-dns-server