# Connectivity issues with a new/upgraded 2.X cluster? Read here first :)

**URL:** <https://discuss.elastic.co/t/connectivity-issues-with-a-new-upgraded-2-x-cluster-read-here-first/35699>\
**Category:** Elasticsearch\
**Created:** [November 27, 2015, 1:44am UTC](https://discuss.elastic.co/t/connectivity-issues-with-a-new-upgraded-2-x-cluster-read-here-first/35699 "2015-11-27T01:44:23Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![Python\_Coder](https://avatars.discourse-cdn.com/v4/letter/p/aeb1de/32.png) [@Python\_Coder](https://discuss.elastic.co/u/Python_Coder)\
**Post date:** [February 21, 2016, 11:22am UTC](https://discuss.elastic.co/t/connectivity-issues-with-a-new-upgraded-2-x-cluster-read-here-first/35699/8 "2016-02-21T11:22:51Z")

</div>

are you sure that the host resolution evaluates to the Non-loopback IP address on node Gee?

---

_[View the full topic](https://discuss.elastic.co/t/connectivity-issues-with-a-new-upgraded-2-x-cluster-read-here-first/35699)._
