# Elastic Search - Lookup Nodes

**URL:** <https://discuss.elastic.co/t/elastic-search-lookup-nodes/233126>\
**Category:** Elasticsearch\
**Created:** [May 18, 2020, 2:23pm UTC](https://discuss.elastic.co/t/elastic-search-lookup-nodes/233126 "2020-05-18T14:23:30Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![nages](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nages/32/46943_2.png) [@nages](https://discuss.elastic.co/u/nages)\
**Post date:** [May 18, 2020, 2:23pm UTC](https://discuss.elastic.co/t/elastic-search-lookup-nodes/233126/1 "2020-05-18T14:23:31Z")

</div>

I am going through the documentation of network settings - I had few queries with respect to the best practices .

1. Should the nodes be assigned static ip address for other nodes to reach out reliably or
2. DNS lookup
3. Doesn't matter the nodes going up or down

What should be the best practise

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [May 18, 2020, 10:53pm UTC](https://discuss.elastic.co/t/elastic-search-lookup-nodes/233126/2 "2020-05-18T22:53:07Z")

</div>

Do you mean coordinating nodes?

You'd be better off using DNS with multiple cnames, or a loadbalancer. That way you can add/remove nodes as needed and not have to change your clients.

---

<div class="post-metadata">

**Author:** ![nages](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nages/32/46943_2.png) [@nages](https://discuss.elastic.co/u/nages)\
**Post date:** [May 19, 2020, 1:55am UTC](https://discuss.elastic.co/t/elastic-search-lookup-nodes/233126/3 "2020-05-19T01:55:15Z")

</div>

is the same applies for within the cluster to avoid depending on IP addresses for look ups ?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [May 19, 2020, 1:55am UTC](https://discuss.elastic.co/t/elastic-search-lookup-nodes/233126/4 "2020-05-19T01:55:49Z")

</div>

What version are you on?

---

<div class="post-metadata">

**Author:** ![nages](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nages/32/46943_2.png) [@nages](https://discuss.elastic.co/u/nages)\
**Post date:** [May 19, 2020, 2:27am UTC](https://discuss.elastic.co/t/elastic-search-lookup-nodes/233126/5 "2020-05-19T02:27:07Z")

</div>

6.8.8

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [May 19, 2020, 11:43pm UTC](https://discuss.elastic.co/t/elastic-search-lookup-nodes/233126/6 "2020-05-19T23:43:25Z")

</div>

It's really up to you how you manage this. It might make sense for your use case, but if you have your cluster deployment automated, it probably won't matter a lot.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [June 16, 2020, 11:43pm UTC](https://discuss.elastic.co/t/elastic-search-lookup-nodes/233126/7 "2020-06-16T23:43:28Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.