# Xip.io should include public network **URL:** \ **Category:** Elastic Cloud Enterprise (ECE)\ **Created:** [February 20, 2017, 2:49am UTC](https://discuss.elastic.co/t/xip-io-should-include-public-network/75659 "2017-02-20T02:49:04Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![m-kiuchi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/m-kiuchi/32/15219_2.png) [@m-kiuchi](https://discuss.elastic.co/u/m-kiuchi)\ **Post date:** [February 20, 2017, 2:49am UTC](https://discuss.elastic.co/t/xip-io-should-include-public-network/75659/1 "2017-02-20T02:49:04Z")
Hi guys, I've beed tring ECE alpha4, and client cannot reach elasticsearch cluster. Endpoint URL shows like that. https://.\.xip.io:...... I think that public network(comes from "Public Hostname") is reachable from customer, and private network(comes from "Host IP") should be hidden from customer. Do I have any misunderstanding ? Please have your comment. BR MK ---
**Author:** ![uricohen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/uricohen/32/9776_2.png) [@uricohen](https://discuss.elastic.co/u/uricohen)\ **Post date:** [February 20, 2017, 9:09am UTC](https://discuss.elastic.co/t/xip-io-should-include-public-network/75659/2 "2017-02-20T09:09:08Z")
Hi @m-kiuchi In general, cluster URLs are in the form of `.`. The CNAME should resolve in the customer's environment to either an ECE proxy or a load balancer that fronts one or more ECE proxies, using a wildcard DNS entry. By default, to allow for easier testing, we mimicked that by using a service called [xip.io](http://xip.io). [xip.io](http://xip.io) provides a generic wildcard DNS service, so for example if you query a hostname like `1234rdsfascd.192.168.1.12.xip.io` it will resolve to `192.168.1.12`. This is just a simple way of providing a reasonable out of the box experience without requiring you to define wildcard DNS entries when you're only evaluating ECE. It does however require the host that access the cluster to have internet connectivity so it can reach [xip.io](http://xip.io), and it needs to be able to route to the proxy IP address as returned by [xip.io](http://xip.io) (in the example above that would be `192.168.1.12`). Note that since we encountered a few cases where [xip.io](http://xip.io) was intermittently unavailable, in the upcoming beta release we will replace [xip.io](http://xip.io) with an Elastic owned service that does the same thing ([ip.es.io](http://ip.es.io)). HTH, Uri ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 6, 2017, 9:09am UTC](https://discuss.elastic.co/t/xip-io-should-include-public-network/75659/3 "2017-03-06T09:09:11Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.