What happens(happened) to "mongodb.net"?

MongoDB Atlas
2

Any clusters are subdomains of mongodb.net so this would be expected behavior.

Atlas connections stings are SRV and TXT records and have to be queried specifically for those. The cluster servers are hosted on subdomains.

And of course the cluster and the dns entries for it could have been deleted.

As you can see everything is working fine. My M0 records for example:

dig +short txt cluster0.9qfvh.mongodb.net
"authSource=admin&replicaSet=Cluster0-shard-0"

dig +short srv _mongodb._tcp.cluster0.9qfvh.mongodb.net
0 0 27017 cluster0-shard-00-02.9qfvh.mongodb.net.
0 0 27017 cluster0-shard-00-01.9qfvh.mongodb.net.
0 0 27017 cluster0-shard-00-00.9qfvh.mongodb.net.

for h in $(dig +short srv _mongodb._tcp.cluster0.9qfvh.mongodb.net | cut -d' ' -f 4)
do dig +short ${h}
done
mtm-aws-useast1-5-m0-16-shard-00-00.xlpjl.mongodb.net.
ec2-3-95-113-226.compute-1.amazonaws.com.
3.95.113.226
mtm-aws-useast1-5-m0-16-shard-00-01.xlpjl.mongodb.net.
ec2-3-94-178-87.compute-1.amazonaws.com.
3.94.178.87
mtm-aws-useast1-5-m0-16-shard-00-02.xlpjl.mongodb.net.
ec2-18-210-201-78.compute-1.amazonaws.com.
18.210.201.78
1 Like