# FDB client connects to old IP addresses

**URL:** <https://forums.foundationdb.org/t/fdb-client-connects-to-old-ip-addresses/3866>\
**Category:** Using FoundationDB\
**Created:** [March 20, 2023, 9:32pm UTC](https://forums.foundationdb.org/t/fdb-client-connects-to-old-ip-addresses/3866 "2023-03-20T21:32:12Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ntrhieu89](https://sea1.discourse-cdn.com/foundationdb/user_avatar/forums.foundationdb.org/ntrhieu89/32/587_2.png) [@ntrhieu89](https://forums.foundationdb.org/u/ntrhieu89)\
**Post date:** [March 20, 2023, 9:32pm UTC](https://forums.foundationdb.org/t/fdb-client-connects-to-old-ip-addresses/3866/1 "2023-03-20T21:32:12Z")

</div>

We have our FDB cluster setup in Kubenetes environment.  
When some FDB pods are re-created, their IPs change. However, we found out in our monitoring log that the FDB clients are still attempting to connect to the old IPs.

My questions are:

1. How long after a pod is re-created the FDB client abandons the old IP address? In our case, we still see the client attempts to connect to old IP address after hours / days.
2. If the IP address is re-used for a different FDB cluster, is it possible for the FDB client to undesirably read/write data to the other FDB cluster?

Thanks.

---

<div class="post-metadata">

**Author:** ![markus.pilman](https://sea1.discourse-cdn.com/foundationdb/user_avatar/forums.foundationdb.org/markus.pilman/32/379_2.png) [@markus.pilman](https://forums.foundationdb.org/u/markus.pilman)\
**Post date:** [March 24, 2023, 3:01am UTC](https://forums.foundationdb.org/t/fdb-client-connects-to-old-ip-addresses/3866/2 "2023-03-24T03:01:49Z")

</div>

FDB doesn’t support IP address changes for coordinators. So I don’t think this situation will recover on its own. If the IP address of the coordinators isn’t stable, you would need to use DNS (though I am not sure how stable that feature is yet, someone from Apple might have more insights).

You probably can change to a different set of coordinators as a temporary fix. Afterwards I would recommend you try to keep the coordinator IPs stable until a proper fix has been deployed. Personally I don’t have experience with this problem, so I wouldn’t be the best person to recommend the best way forward.
