Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Hi @chadspecter
If you’re the “Private Networking” function, meaning the IPs starting with 10.x.x.x, then they are only accessible inside the data center.
You should be using those IPs to connect the different databases together, since it will be much faster than using the public IP.
Are you using the CloudFlare protection on those A-records or just the DNS with passthru? You should use the passthru, so nothing gets mumbled by CloudFlare.
Can you run this command to list the services listening:
sudo lsof -iTCP -sTCP:LISTEN -P
I am just using DNS passthrough in Cloudflare. I have not even attempted to enable the private networking addresses yet as I just wanted to get it working over the open IPs first.
Here is the output of sudo lsof -iTCP -sTCP:LISTEN -P
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
sshd 1576 root 3u IPv4 14187 0t0 TCP *:22 (LISTEN)
sshd 1576 root 4u IPv6 14189 0t0 TCP *:22 (LISTEN)
mongod 1804 root 7u IPv4 16752 0t0 TCP localhost:27017 (LISTEN)
mongod 1804 root 9u IPv4 16754 0t0 TCP mongo-01.domain.name:27017 (LISTEN)
OK. So it was the IPv6 thing. I rebuilt the replica set as IPv4 and everything works fine. I guess the ISP my office uses has not upgraded yet. Tried the IPv6 system at home (Verizon Fios) and it worked. Thanks for the help!