Skip to content

docker internal dns use only the first nameserver declare in resolv.conf #20494

Description

@JrCs

Hi,

i have a server with 2 nameservers declare in /etc/resolv.conf.
The first one is the dns from consul to resolve nodes and services and the second is the nameserver to resolve internet adresses.

i create a new network bridge with the command:

docker network create newnetwork

and attach a new container with it

docker run -it --rm --net=newnetwork busybox sh

In that container i can resolve nodes and services return by the dns of consul, but i can't resolv internet adresses.
So i think the internal dns of docker use only the first nameserver declare in resolv.conf instead of using all.

My configuration:

docker version:

Client:
 Version:      1.10.0
 API version:  1.22
 Go version:   go1.4.3
 Git commit:   e21da33
 Built:
 OS/Arch:      linux/amd64

Server:
 Version:      1.10.0
 API version:  1.22
 Go version:   go1.4.3
 Git commit:   e21da33
 Built:
 OS/Arch:      linux/amd64

docker info:

Containers: 72
 Running: 64
 Paused: 0
 Stopped: 8
Images: 75
Server Version: 1.10.0
Storage Driver: btrfs
 Build Version: Btrfs v4.2.2
 Library Version: 101
Execution Driver: native-0.2
Logging Driver: json-file
Plugins:
 Volume: local
 Network: bridge null host
Kernel Version: 4.4.1-coreos
Operating System: CoreOS 955.0.0
OSType: linux
Architecture: x86_64
CPUs: 8
Total Memory: 31.26 GiB
Name: sd-65534
ID: 6F5O:FVKR:FMX3:B6KD:WCIF:3KLF:MYK2:65R5:OEHA:4GZT:RZKF:JTPK
Username: jrcs
Registry: https://index.docker.io/v1/

uname -a:

Linux sd-65534 4.4.1-coreos #2 SMP Thu Feb 11 01:49:47 UTC 2016 x86_64 Intel(R) Xeon(R) CPU E3-1230 v3 @ 3.30GHz GenuineIntel GNU/Linux

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions