# Split Horizon Issue

**URL:** <https://forums.percona.com/t/split-horizon-issue/36040>\
**Category:** Percona Operator for MongoDB\
**Created:** [January 9, 2025, 7:12am UTC](https://forums.percona.com/t/split-horizon-issue/36040 "2025-01-09T07:12:30Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![devopser](https://avatars.discourse-cdn.com/v4/letter/d/48db29/32.png) [@devopser](https://forums.percona.com/u/devopser)\
**Post date:** [January 9, 2025, 7:12am UTC](https://forums.percona.com/t/split-horizon-issue/36040/1 "2025-01-09T07:12:30Z")

</div>

## Description:

MongoDB deployed with Percona Operator with split-horizon DNS doesn’t connect and I get the following error: `MongoServerSelectionError`

## Steps to Reproduce:

1. Installed with latest Helm Percona Operator for MongoDB 6-node multi-cloud (Azure and AWS using NetBird) K8s cluster.
2. Followed the instructions on this blog post (NodePort instructions): [Beyond the Horizon: Mastering Percona Server for MongoDB Exposure in Kubernetes – Part One](https://www.percona.com/blog/beyond-the-horizon-mastering-percona-server-for-mongodb-exposure-in-kubernetes-part-one/)

## Additional Information:

1. The `psmdb` state is ready and I was able to connct to the database using the certificates but with the replica set’s internal DNS “`<cluster-name>-rs0.<namespace>.svc.cluster.local`”
2. The DNS is correctly resolving the VM’s IP address as I can access other services runnning on other ports using it
3. All K8s NodePorts traffic are allowed
4. When I tried to use `nc` to check access to the pods’ NodePort ports I got connection timeout error

## Expected Result:

The `mongosh` CLI should be able to connect using the split horizon DNS