# Service - Static IP

**URL:** <https://forums.suse.com/t/service-static-ip/1514>\
**Category:** Rancher 1.x\
**Created:** [January 22, 2016, 4:23pm UTC](https://forums.suse.com/t/service-static-ip/1514 "2016-01-22T16:23:44Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jaybee](https://avatars.discourse-cdn.com/v4/letter/j/6de8d8/32.png) [@jaybee](https://forums.suse.com/u/jaybee)\
**Post date:** [January 22, 2016, 4:23pm UTC](https://forums.suse.com/t/service-static-ip/1514/1 "2016-01-22T16:23:44Z")

</div>

Hi,

I’m using Rancher and I’m really happy with it!

I’ve an orchestrator (x.x.x.155), and three nodes (x.x.x.156…158).  
When I create a service, depending on the each node load, the container can be hosted in any node. When I restart the service for example, the host can change and its IP.  
Let’s say I have one web application with the host/private port 80:80.  
How can I set a static IP to link with a linked service?  
Maybe my question seems stupid but I tried with a load balancer and it doesn’t work…

---

<div class="post-metadata">

**Author:** ![alena](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/alena/32/50_2.png) [@alena](https://forums.suse.com/u/alena)\
**Post date:** [January 22, 2016, 5:59pm UTC](https://forums.suse.com/t/service-static-ip/1514/2 "2016-01-22T17:59:57Z")

</div>

@jaybee we don’t have static ip concept in Rancher today. There are a couple of workarounds to support your use case:

- pin service to deploy to a particular host by setting scheduling labels on the service. This way the service’s containers will get deployed only on particular host (or set of hosts)
- Use Rancher Route53 service which will publish Service FQDN to AWS Route53, and will manage host ips records for this fqdn based on the service’s deployment: [http://rancher.com/introducing-rancher-service-discovery-integration-with-amazon-route53/](http://rancher.com/introducing-rancher-service-discovery-integration-with-amazon-route53/)