Rancher internal DNS not working

We just started to test Rancher to use it on our infrastucture. We are very happy but maybe we are doing something wrong because we can’t go ahead because this problem.

I am going to detail all steps here.

I started a clean install of Rancher on Centos 7.2 on a bare metal server.


  • Installed docker-engine 1.9.1
    yum install docker-engine -y

  • Installed Rancher server
    docker run -d -v /data/mysql:/var/lib/mysql --restart=always -p 8080:8080 rancher/server

  • Rancher version installed:
    Component Version Rancher v0.50.0 Cattle v0.126.0 User Interface v0.74.0 Rancher Compose v0.6.2

  • Access to the server via rancher.test.com:8080

  • Add a new host via ui option with custom.
    sudo docker run -d --privileged -v /var/run/docker.sock:/var/run/docker.sock rancher/agent:v0.8.2 http://rancher.test.com:8080/v1/scripts/0D96A3705AAC136E7B9C:1450285200000:7JqtNwHQQblCIZ6IjZtsuTm5LA

  • Started a service with
    image: ubuntu:14.04.3
    command: bash

  • List the containers with docker ps:
    CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 59063c783744 ubuntu:14.04.3 "bash" 17 minutes ago Up 17 minutes b0b3f2bf-0eed-468b-b03d-7d41fdd5d309 d2e5d2ad2218 rancher/agent-instance:v0.6.0 "/etc/init.d/agent-in" 18 minutes ago Up 18 minutes>500/udp,>4500/udp 670c73ba-059f-49de-a302-833a216f87b3 f382f587e3e3 rancher/agent:v0.8.2 "/run.sh run" 21 minutes ago Up 21 minutes rancher-agent 5fe6cce4ba4f rancher/server "/usr/bin/s6-svscan /" 25 minutes ago Up 25 minutes 3306/tcp,>8080/tcp sad_meitner

  • Access to container:
    docker exec -it b0b3f2bf-0eed-468b-b03d-7d41fdd5d309 bash

  • Watch the file /etc/resolv.conf
    # nameserver search ovh.net rancher.internal nameserver

  • Use dig command to test dns
    root@59063c783744:/# dig rancher-metadata ;; reply from unexpected source:, expected

We can’t ping any server and we can not connect to anything.
Has anyone the same problem or maybe similar? Any help with this could be great.

Thanks you for your help.