# Transport.publish\_host and network.publish\_host

**URL:** <https://discuss.elastic.co/t/transport-publish-host-and-network-publish-host/84332>\
**Category:** Elasticsearch\
**Created:** [May 2, 2017, 11:14pm UTC](https://discuss.elastic.co/t/transport-publish-host-and-network-publish-host/84332 "2017-05-02T23:14:29Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![YuWatanabe](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yuwatanabe/32/13259_2.png) [@YuWatanabe](https://discuss.elastic.co/u/YuWatanabe)\
**Post date:** [May 2, 2017, 11:14pm UTC](https://discuss.elastic.co/t/transport-publish-host-and-network-publish-host/84332/1 "2017-05-02T23:14:30Z")

</div>

I appreciate if someone can help me out .

I have read two sections in the reference but did not understand in what situations network.publish\_host (9200/tcp) is used between the nodes.

transport module is clearly stated in below section,  
[https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-transport.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-transport.html)

however, below section does not state the usage of 9200/tcp between the nodes.

[https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-network.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-network.html)

So my question is , in what situations does nodes use **9200/tcp** for its internal communications?

---

<div class="post-metadata">

**Author:** ![nik9000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik9000/32/44947_2.png) [@nik9000](https://discuss.elastic.co/u/nik9000)\
**Post date:** [May 2, 2017, 11:53pm UTC](https://discuss.elastic.co/t/transport-publish-host-and-network-publish-host/84332/2 "2017-05-02T23:53:57Z")

</div>

Tcp/9200 is the default port for nodes to listen to for the internode  
protocol. All nodes in a cluster connect to every other node using that  
port.

Usually the host we listen to and the publish host should be the same. The  
only time you should need to configure the publish host is when the nodes  
have something between them.

---

<div class="post-metadata">

**Author:** ![YuWatanabe](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yuwatanabe/32/13259_2.png) [@YuWatanabe](https://discuss.elastic.co/u/YuWatanabe)\
**Post date:** [May 3, 2017, 12:31am UTC](https://discuss.elastic.co/t/transport-publish-host-and-network-publish-host/84332/3 "2017-05-03T00:31:30Z")

</div>

nik9000

Thank you for the reply.

I have a customer who chooses to split the network for node internal  
communication and log ingestion. I will use publish\_host for my case.

---

<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:** [May 31, 2017, 12:37am UTC](https://discuss.elastic.co/t/transport-publish-host-and-network-publish-host/84332/4 "2017-05-31T00:37:14Z")

</div>

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