Atlas-MongoDB Connection 🗄️¶
This page provides guidance for connecting to MongoDB Atlas clusters, interpreting DNS responses, and troubleshooting common connectivity issues.
🧩 DNS Response for MongoDB Atlas SRV Record¶
To resolve the SRV record for your Atlas cluster, use the following command:
dig SRV _mongodb._tcp.atnt-pl-0.bw4zj.mongodb.net
_mongodb._tcp.atnt-pl-0.bw4zj.mongodb.net. 60 IN SRV 0 0 1034 pl-0-us-east-1.bw4zj.mongodb.net.
_mongodb._tcp.atnt-pl-0.bw4zj.mongodb.net. 60 IN SRV 0 0 1035 pl-0-us-east-1.bw4zj.mongodb.net.
_mongodb._tcp.atnt-pl-0.bw4zj.mongodb.net. 60 IN SRV 0 0 1036 pl-0-us-west-2.bw4zj.mongodb.net.
SRV Records
SRV records provide the hostnames and ports for your MongoDB cluster nodes. Ensure your DNS resolver can access these records.
🛠️ Troubleshooting MongoDB Atlas Connection Issues¶
If you encounter connection errors, check the following:
Network Access List: Ensure your IP or VPC is allowed in the Atlas Network Access List.
DNS Resolution: Confirm that your environment can resolve Atlas hostnames.
Firewall Rules: Verify that outbound traffic to Atlas cluster ports is permitted.
🔗 https://www.mongodb.com/docs/atlas/troubleshoot-connection/
Example Error and Diagnostic Steps:
mongosh "mongodb://atnt-pl-0.bw4zj.mongodb.net/" --apiVersion 1 --username unibeam
dig SRV _mongodb._tcp.atnt-pl-0.bw4zj.mongodb.net
_mongodb._tcp.atnt-pl-0.bw4zj.mongodb.net. 60 IN SRV 0 0 1034 pl-0-us-east-1.bw4zj.mongodb.net.
_mongodb._tcp.atnt-pl-0.bw4zj.mongodb.net. 60 IN SRV 0 0 1035 pl-0-us-east-1.bw4zj.mongodb.net.
_mongodb._tcp.atnt-pl-0.bw4zj.mongodb.net. 60 IN SRV 0 0 1036 pl-0-us-west-2.bw4zj.mongodb.net.
Warning
"DNS Resolution" If you receive ENOTFOUND errors, verify your pod's DNS configuration and ensure it can resolve Atlas hostnames.
🔗 Useful Resources¶
MongoDB Atlas Troubleshoot Connection
## Atlas-MongoDB Connection 🗄️
This page provides guidance for connecting to MongoDB Atlas clusters, interpreting DNS responses, and troubleshooting common connectivity issues.
---
### 🧩 DNS Response for MongoDB Atlas SRV Record
To resolve the SRV record for your Atlas cluster, use the following command:
```bash
dig SRV _mongodb._tcp.atnt-pl-0.bw4zj.mongodb.net
Sample Output:
_mongodb._tcp.atnt-pl-0.bw4zj.mongodb.net. 60 IN SRV 0 0 1034 pl-0-us-east-1.bw4zj.mongodb.net.
_mongodb._tcp.atnt-pl-0.bw4zj.mongodb.net. 60 IN SRV 0 0 1035 pl-0-us-east-1.bw4zj.mongodb.net.
_mongodb._tcp.atnt-pl-0.bw4zj.mongodb.net. 60 IN SRV 0 0 1036 pl-0-us-west-2.bw4zj.mongodb.net.
SRV Records
SRV records provide the hostnames and ports for your MongoDB cluster nodes. Ensure your DNS resolver can access these records.
🛠️ Troubleshooting MongoDB Atlas Connection Issues¶
If you encounter connection errors, check the following:
-
Network Access List:
Ensure your IP or VPC is allowed in the Atlas Network Access List. -
DNS Resolution:
Confirm that your environment can resolve Atlas hostnames. -
Firewall Rules:
Verify that outbound traffic to Atlas cluster ports is permitted.
Example Error and Diagnostic Steps:
[root@ip-172-23-6-244 /]# mongosh -u unibeam -p EatlIeHbNcNTHaW --host pl-0-us-east-1.bw4zj.mongodb.net:1034,pl-0-us-east-1.bw4zj.mongodb.net:1035
MongoServerSelectionError: connection <monitor> to 172.23.11.14:1034 closed. It looks like this is a MongoDB Atlas cluster. Please ensure that your Network Access List allows connections from your IP.
[root@ip-172-23-6-244 /]# nc -zv 172.23.11.14 1034
Ncat: Connected to 172.23.11.14:1034.
Connection Error
If you see MongoServerSelectionError, check your Atlas Network Access List and confirm your source IP is permitted.
🔍 Connectivity Test from EKS Pod¶
Test connectivity from your Kubernetes pod using mongosh and dig:
mongosh "mongodb://atnt-pl-0.bw4zj.mongodb.net/" --apiVersion 1 --username unibeam
dig SRV _mongodb._tcp.atnt-pl-0.bw4zj.mongodb.net
Sample DNS Output:
_mongodb._tcp.atnt-pl-0.bw4zj.mongodb.net. 60 IN SRV 0 0 1035 pl-0-us-east-1.bw4zj.mongodb.net.
_mongodb._tcp.atnt-pl-0.bw4zj.mongodb.net. 60 IN SRV 0 0 1036 pl-0-us-west-2.bw4zj.mongodb.net.
_mongodb._tcp.atnt-pl-0.bw4zj.mongodb.net. 60 IN SRV 0 0 1034 pl-0-us-east-1.bw4zj.mongodb.net.
DNS Resolution
If you receive ENOTFOUND errors, verify your pod's DNS configuration and ensure it can resolve Atlas hostnames.
🔗 Useful Resources¶
Further Reading
Refer to the official MongoDB Atlas documentation for advanced troubleshooting and best practices.