# High availability setup with Round Robin DNS **URL:** \ **Category:** Rancher 1.x\ **Created:** [July 5, 2016, 9:20pm UTC](https://forums.suse.com/t/high-availability-setup-with-round-robin-dns/3322 "2016-07-05T21:20:53Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![richardoflynn](https://avatars.discourse-cdn.com/v4/letter/r/ee7513/32.png) [@richardoflynn](https://forums.suse.com/u/richardoflynn)\ **Post date:** [July 5, 2016, 9:20pm UTC](https://forums.suse.com/t/high-availability-setup-with-round-robin-dns/3322/1 "2016-07-05T21:20:53Z")
Hi, we are setting up a test environment, we rancherOS on 3 bare metal servers, and have setup percona cluster on each. Next we successfully launched rancher on one node. We dont have an external load balancer, we have set up round robin dns for the 3 machines to be accessible from a single domain. However, this seems to be a problem when trying to run the [rancher-ha.sh](http://rancher-ha.sh) script. The logs are just spewing: Can not launch agent right now: Server not available at [http://172.17.0.1:18080/ping:](http://172.17.0.1:18080/ping:)" component=service Is it simply not do-able? or is there a work around or indeed is something else a miss? all latest code. (v0.5.0 // rancher/server:v1.1.0) I have tried editing the [rancher-ha.sh](http://rancher-ha.sh) script to add -p 8080:8080 -p 443:443 -p 18080:18080 to the docker run command but this made no change. Im not quite sure what the route cause is? I have also tried setting docker run -e CATTLE\_AGENT\_IP=host\_ip… and export CATTLE\_AGENT\_IP=host\_ip both in rancher\_ha. I also tried setting the CATTLE\_HA\_HOST\_REGISTRATION\_URL to include the :8080 and to run on http since round robin would not be doing the same port forwarding as a load balancer. I have spent two days solid tearing this up and down it is so frustrating. Thanks ---
**Author:** ![Rick\_Balwani](https://avatars.discourse-cdn.com/v4/letter/r/e19b73/32.png) [@Rick\_Balwani](https://forums.suse.com/u/Rick_Balwani)\ **Post date:** [July 20, 2016, 9:59pm UTC](https://forums.suse.com/t/high-availability-setup-with-round-robin-dns/3322/2 "2016-07-20T21:59:12Z")
I am also experiencing the same exact issues… And have tried all of the above steps with no luck… ---
**Author:** ![aemneina](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/aemneina/32/1323_2.png) [@aemneina](https://forums.suse.com/u/aemneina)\ **Post date:** [July 22, 2016, 5:20pm UTC](https://forums.suse.com/t/high-availability-setup-with-round-robin-dns/3322/3 "2016-07-22T17:20:05Z")
We don’t recommend using round robin DNS for any real HA setup. It might work but wont be adequate for a large number of reasons. Any reason why you wouldnt be using something designed for load balancing, like HA Proxy, ELB, etc…? ---
**Author:** ![richardoflynn](https://avatars.discourse-cdn.com/v4/letter/r/ee7513/32.png) [@richardoflynn](https://forums.suse.com/u/richardoflynn)\ **Post date:** [July 22, 2016, 5:55pm UTC](https://forums.suse.com/t/high-availability-setup-with-round-robin-dns/3322/4 "2016-07-22T17:55:45Z")
For me its just a test environment, I have 3 bare metal servers to cluster, and it saved me placing another piece of hardware in front of them. What are the large number of reasons? In summary format if you don’t mind taking the time? ---
**Author:** ![Rick\_Balwani](https://avatars.discourse-cdn.com/v4/letter/r/e19b73/32.png) [@Rick\_Balwani](https://forums.suse.com/u/Rick_Balwani)\ **Post date:** [July 28, 2016, 8:46pm UTC](https://forums.suse.com/t/high-availability-setup-with-round-robin-dns/3322/5 "2016-07-28T20:46:19Z")
My issues stopped when i switched to rhel7.2… I was previously using centos7