# Rancher-metadata not resolving

**URL:** <https://forums.suse.com/t/rancher-metadata-not-resolving/5866>\
**Category:** General\
**Created:** [March 16, 2017, 11:48am UTC](https://forums.suse.com/t/rancher-metadata-not-resolving/5866 "2017-03-16T11:48:56Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![adamgraves-choices](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/adamgraves-choices/32/2041_2.png) [@adamgraves-choices](https://forums.suse.com/u/adamgraves-choices)\
**Post date:** [March 16, 2017, 11:48am UTC](https://forums.suse.com/t/rancher-metadata-not-resolving/5866/1 "2017-03-16T11:48:56Z")

</div>

Hi,

We’re using the traefik load balancer in some of our environments, which uses the rancher-metadata service to update it’s config dynamically.

We’ve now had two incidents where the load balancer has stopped updating. The first time we migrated to a new rancher environment which fixed the issue, but recreating the infra stacks and the load balancer stack didn’t fix the issue.

This time we’ve done a bit more investigation and it seems that none of the containers can resolve rancher-metadata anymore. Restarting the containers and the infrastructure stacks seems to have made a difference.

We can resolve rancher-metadata.rancher.internal though.

/ # curl [http://rancher-metadata](http://rancher-metadata)  
curl: (6) Couldn’t resolve host ‘rancher-metadata’  
/ # curl [http://rancher-metadata.rancher.internal](http://rancher-metadata.rancher.internal)  
2015-07-25  
2015-12-19  
2016-07-29  
latest

Any ideas?

We’re running Rancher Server v1.5.1

---

<div class="post-metadata">

**Author:** ![adamgraves-choices](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/adamgraves-choices/32/2041_2.png) [@adamgraves-choices](https://forums.suse.com/u/adamgraves-choices)\
**Post date:** [March 16, 2017, 12:16pm UTC](https://forums.suse.com/t/rancher-metadata-not-resolving/5866/2 "2017-03-16T12:16:13Z")

</div>

That would have suggested that the DNS search domain isn’t set, but it looks like it is:

```
/ # cat /etc/resolv.conf
search nginx.rancher.internal test.nginx.rancher.internal rancher.internal ntj
jgslkbwcujjrdy3bc44bfzg.zx.internal.cloudapp.net
nameserver 169.254.169.250

/ # ping rancher-metadata.rancher.internal
PING rancher-metadata.rancher.internal (169.254.169.250): 56 data bytes
64 bytes from 169.254.169.250: seq=0 ttl=63 time=0.082 ms
^C
--- rancher-metadata.rancher.internal ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max = 0.082/0.082/0.082 ms

/ # ping rancher-metadata
`ping: bad address 'rancher-metadata'
```

---

<div class="post-metadata">

**Author:** ![leodotcloud](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/leodotcloud/32/3103_2.png) [@leodotcloud](https://forums.suse.com/u/leodotcloud)\
**Post date:** [March 17, 2017, 4:50am UTC](https://forums.suse.com/t/rancher-metadata-not-resolving/5866/3 "2017-03-17T04:50:29Z")

</div>

@adamgraves-choices is your container based on alpine?

---

<div class="post-metadata">

**Author:** ![zicklag](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/zicklag/32/2095_2.png) [@zicklag](https://forums.suse.com/u/zicklag)\
**Post date:** [May 6, 2017, 10:35pm UTC](https://forums.suse.com/t/rancher-metadata-not-resolving/5866/4 "2017-05-06T22:35:46Z")

</div>

> [@leodotcloud](#):
>
> is your container based on alpine?

I have alpine containers that are not resolving `http://rancher-metadata` do you know why this is? It is the same deal as @adamgraves-choices, `http://rancher-metadata.rancher.internal` will resolve.