The cluster cluster0-tehz2 does not seem to be setup correctly.
: steevej @ asus-laptop ; dig any _mongodb._tcp.cluster0-tehz2.mongodb.net ; <> DiG 9.16.1 <> any _mongodb._tcp.cluster0-tehz2.mongodb.net ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 45103 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;_mongodb._tcp.cluster0-tehz2.mongodb.net. IN ANY ;; AUTHORITY SECTION: mongodb.net. 899 IN SOA ns-761.awsdns-31.net. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 60
We usually get the info about the replica set nodes forming the cluster as in:
: steevej @ asus-laptop ; dig any _mongodb._tcp.cluster0-xahr1.mongodb.net ; <> DiG 9.16.1 <> any _mongodb._tcp.cluster0-xahr1.mongodb.net ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52529 ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;_mongodb._tcp.cluster0-xahr1.mongodb.net. IN ANY ;; ANSWER SECTION: _mongodb._tcp.cluster0-xahr1.mongodb.net. 59 IN SRV 0 0 27017 cluster0-shard-00-00-xahr1.mongodb.net. _mongodb._tcp.cluster0-xahr1.mongodb.net. 59 IN SRV 0 0 27017 cluster0-shard-00-01-xahr1.mongodb.net. _mongodb._tcp.cluster0-xahr1.mongodb.net. 59 IN SRV 0 0 27017 cluster0-shard-00-02-xahr1.mongodb.net.