# Proposal: Don't identify a coordinator based on its IP

**URL:** <https://forums.foundationdb.org/t/proposal-dont-identify-a-coordinator-based-on-its-ip/502>\
**Category:** FoundationDB Core\
**Created:** [June 9, 2018, 1:09pm UTC](https://forums.foundationdb.org/t/proposal-dont-identify-a-coordinator-based-on-its-ip/502 "2018-06-09T13:09:51Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![Chr1st0ph](https://sea1.discourse-cdn.com/foundationdb/user_avatar/forums.foundationdb.org/chr1st0ph/32/353_2.png) [@Chr1st0ph](https://forums.foundationdb.org/u/Chr1st0ph)\
**Post date:** [August 7, 2018, 6:33am UTC](https://forums.foundationdb.org/t/proposal-dont-identify-a-coordinator-based-on-its-ip/502/12 "2018-08-07T06:33:04Z")

</div>

I believe we need another feature based on DNS: support for “seeds identifited by hostnames”.

Thus, you do not have to “copy” the fdb.cluster file in Kubernetes for adding new nodes. You just define one or few seed nodes ( probably coordinators ), and these seed nodes provide the necessary topology information for new nodes and applications.

What are your thoughts ?

---

_[View the full topic](https://forums.foundationdb.org/t/proposal-dont-identify-a-coordinator-based-on-its-ip/502)._