Atlas Private DNS Zones Azure
Parent: MongoDB Atlas on Azure · Published reference · snapshot 2026-10-23 · skill mongodb-cohort-fb5f4021932f
↓ Facts as markdownall context files
Source-anchored research for Atlas Private DNS Zones Azure. Run status: COMPLETED.
These notes link each claim to its source. Some citations identify archived research reports that are no longer hosted on this site. A published reference means the content is available; it does not certify independent review or accuracy.Read the editorial policy and follow the sources before relying on a claim.
How it works
- When diagnosing an Azure Atlas SRV connection, inspect the _mongodb._tcp seedlist and then resolve its returned target hostname. The expected combination is Atlas-assigned node ports and the endpoint NIC's private IP; checking only one A record misses service discovery. (medium confidence) [source]
Problems, failure modes and limitations
- Manually freezing SRV ports creates maintenance risk: Atlas documents that Azure Private Link ports can change after cluster changes and recommends the DNS seedlist private endpoint-aware connection string. A custom copy needs a process to track those changes. (medium confidence) [source]
- A July 2024 user reported that an Azure Atlas private endpoint hostname resolved publicly to the VNet's private IP. This is an observation from one deployment; the thread does not establish a configuration error or a general Atlas disclosure policy. (low confidence) [source]
- Creating a local Azure Private DNS Zone does not change Atlas's authoritative public DNS answers. A Microsoft Q&A exchange explicitly says Azure cannot control the third party's public publication of private endpoint addresses. (low confidence) [source]
Comparisons and alternatives
- If creating an Atlas DNS override, scope the zone to the actual cluster-specific suffix, such as uzgh6.mongodb.net, rather than the entire mongodb.net namespace. Broad overrides can shadow unrelated public names and cause resolution failures. (high confidence) [source]
Facts and statements
- For Azure Private Link, Atlas publishes private endpoint-aware connection strings: SRV records identify distinct node ports on a shared hostname, and that hostname's A record resolves to the private endpoint NIC's private IP. (high confidence) [source]
- Azure Private DNS Zones can manually map Atlas endpoint hostnames to private IPs. The zone must be linked to the application's VNet for Azure DNS to serve those private records. (high confidence) [source]
- The February 2026 walkthrough constructs a custom Atlas zone with an A record for the endpoint IP, SRV records derived from endpoint connection-string ports, and a TXT record containing authSource and replicaSet options. (low confidence) [source]
Children
- No children recorded.