# DNS: Resolve service on same host

**URL:** <https://forums.suse.com/t/dns-resolve-service-on-same-host/2974>\
**Category:** Rancher 1.x\
**Created:** [May 31, 2016, 10:16am UTC](https://forums.suse.com/t/dns-resolve-service-on-same-host/2974 "2016-05-31T10:16:34Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![neuni](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/neuni/32/1386_2.png) [@neuni](https://forums.suse.com/u/neuni)\
**Post date:** [May 31, 2016, 10:16am UTC](https://forums.suse.com/t/dns-resolve-service-on-same-host/2974/1 "2016-05-31T10:16:34Z")

</div>

Hi,

how can I reach a service / sidekick container on the same host?  
I need HTTP communication between my services, but they should only use services on the same host. Currently my services run on two hosts and I get responses from different IPs when I ping other containers by name.  
Current setup:  
Primary container (varnish) + 2 Sidekicks (nginx, phpfpm) on 2 hosts (A & B). When pinging “nginx” from varnish, I get responses from nginx on Host A and Host B.

---

<div class="post-metadata">

**Author:** ![denise](https://avatars.discourse-cdn.com/v4/letter/d/82dd89/32.png) [@denise](https://forums.suse.com/u/denise)\
**Post date:** [June 2, 2016, 6:45pm UTC](https://forums.suse.com/t/dns-resolve-service-on-same-host/2974/2 "2016-06-02T18:45:36Z")

</div>

You would not be able to explicitly reach the single sidekick container. Our internal DNS will round robin between all the containers in the service.

If you wanted it to be host specific, you’d need to create 2 different services (with sidekicks) on each host.

---

<div class="post-metadata">

**Author:** ![RVN\_BR](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/rvn_br/32/2842_2.png) [@RVN\_BR](https://forums.suse.com/u/RVN_BR)\
**Post date:** [November 21, 2017, 6:41pm UTC](https://forums.suse.com/t/dns-resolve-service-on-same-host/2974/3 "2017-11-21T18:41:20Z")

</div>

Sorry to bring this up again, but I seem to remember reading abt something similar in the docs but cant find it now… (as in a special DNS suffix to reach containers on same host primarily)… does this exist or am I dreaming?
