# Kibana elasticsearch\_url **URL:** \ **Category:** Kibana\ **Created:** [June 21, 2015, 6:35pm UTC](https://discuss.elastic.co/t/kibana-elasticsearch-url/24048 "2015-06-21T18:35:05Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![tgdesrochers](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tgdesrochers/32/51322_2.png) [@tgdesrochers](https://discuss.elastic.co/u/tgdesrochers)\ **Post date:** [June 21, 2015, 6:35pm UTC](https://discuss.elastic.co/t/kibana-elasticsearch-url/24048/1 "2015-06-21T18:35:06Z")
I have a production ELK environment and I want to have multiple kibana search load balancers. Right now I have two nodes set to not become master and not have data. I have places those 2 IP's in their own domain but when I edit the kibana.yml file and change the setting from: elasticsearch\_url: "[http://localhost:9200](http://localhost:9200)" to elasticsearch\_url: "[http://lDOMAIN:9200](http://lDOMAIN:9200)" I cannot get kibana to load any longer. The question is I guess, do I need to put a FQDN in that section to load balance my searches or with multiple nodes set up as balancers will elasticsearch automatically balance my searches across all nodes that are set up that way. I want an easy way to be able to scale up more load balancers if we get to a point when our searches are getting slowed down because of the load we are putting on the cluster. Thanks Tim ---
**Author:** ![eperry](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eperry/32/551_2.png) [@eperry](https://discuss.elastic.co/u/eperry)\ **Post date:** [June 21, 2015, 7:00pm UTC](https://discuss.elastic.co/t/kibana-elasticsearch-url/24048/2 "2015-06-21T19:00:31Z")
For the domain issue as long as it resolves on your local system such as "ping" command your good. You might check that the elasticsearch is actually listening on your new IP's with **netstat -nltp** you could be bound to localhost and not the public address I like to test with Netcat **nc -zv host 9200** ---
**Author:** ![tgdesrochers](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tgdesrochers/32/51322_2.png) [@tgdesrochers](https://discuss.elastic.co/u/tgdesrochers)\ **Post date:** [June 21, 2015, 7:21pm UTC](https://discuss.elastic.co/t/kibana-elasticsearch-url/24048/3 "2015-06-21T19:21:38Z")
Thanks, turns out it is a DNS issue. I just have to set up a zone transfer and it should work. Thanks for the reply. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 2:17pm UTC](https://discuss.elastic.co/t/kibana-elasticsearch-url/24048/4 "2017-07-06T14:17:46Z")