# Using LB for discovery.zen.ping.unicast.hosts no longer works?

**URL:** <https://discuss.elastic.co/t/using-lb-for-discovery-zen-ping-unicast-hosts-no-longer-works/252740>\
**Category:** Elasticsearch\
**Created:** [October 20, 2020, 9:19pm UTC](https://discuss.elastic.co/t/using-lb-for-discovery-zen-ping-unicast-hosts-no-longer-works/252740 "2020-10-20T21:19:01Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Chris\_Gatihi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chris_gatihi/32/25820_2.png) [@Chris\_Gatihi](https://discuss.elastic.co/u/Chris_Gatihi)\
**Post date:** [October 20, 2020, 9:19pm UTC](https://discuss.elastic.co/t/using-lb-for-discovery-zen-ping-unicast-hosts-no-longer-works/252740/1 "2020-10-20T21:19:01Z")

</div>

Hi,

For a long time I've been able to use a load balancer IP for the `discovery.zen.ping.unicast.hosts` property in `elasticsearch.yml`.

But I just upgraded from 5.6 to 6.8 and after upgrading ES is no longer able to detect other nodes via the LB ip. If I change the LB ip to node ip's it works. But I can't do that because those change. So it seems to be something specific to LB ip's that has changed?

Is this a known change planned from the ES side?

Thanks,  
Chris

---

<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:** [November 17, 2020, 9:19pm UTC](https://discuss.elastic.co/t/using-lb-for-discovery-zen-ping-unicast-hosts-no-longer-works/252740/2 "2020-11-17T21:19:12Z")

</div>

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