Public | Automated Build

Last pushed: 3 years ago
Short Description
Fork of phensley/docker-dns-rest.
Full Description


A RESTful DNS service for Docker containers.

This service is used to cover a specific use cases for testing applications
which rely on DNS for service discovery, and come bundled with configurations
for certain environments.

For example, to fool a service into thinking its running in a staging
environment, we can create several named containers and map one or more domain
names to them. When the containers come online, the dnsrest service maps the
domain names to the container IP addresses and answers DNS queries from the
other containers.


First, start docker-dns-rest container. The docker-dns-rest container listens
on port 80 by default, so depending on how you run Docker you may need to map
a host port:

% docker run -d -p 5080:80 -v /var/run/docker.sock:/docker.sock --name dns \
    phensley/docker-dns-rest --verbose 

Tail the logs:

% docker logs -f dns

Ensure you have routing from your local machine to the docker-dns-rest
container. Assuming you're running Docker under a Vagrant VM on the local
host, add a route to the VM's IP ( in this example):

% route add -net

Get the IP of the DNS container:

% docker inspect -f '{{.NetworkSettings.IPAddress}}' dns

Next, add some names to the DNS registry. We can associate one or more names
with a container by id or name. We'll associate some domain names with
the container name www:

% curl -X PUT \
    -d '{"domains": ["*", ""]}' \
{"code": 0}

Now, start up a container with that name:

% docker run -it --name www ubuntu bash

You should see some output in the DNS log: - - [2014-10-11 15:25:34] "PUT /container/name/www HTTP/1.1" 200 134 0.000366
2014-10-11T15:26:29.198673 [dnsrest] setting www (83854cf229) as active
2014-10-11T15:26:29.198821 [dnsrest] added * ->
2014-10-11T15:26:29.198900 [dnsrest] added ->

Confirm the www container's IP address:

% docker inspect -f '{{.NetworkSettings.IPAddress}}' www

Now you can query some names against the DNS server:

% host
Using domain server:
Aliases: has address has address

When you stop the www container, the names will be unregistered:

% docker stop www

... dns logs ...
2014-10-11T15:28:35.050232 [dnsrest] setting www (83854cf229) as inactive
2014-10-11T15:28:35.050378 [dnsrest] removed * ->
2014-10-11T15:28:35.050462 [dnsrest] removed ->

Now start the www container again and the names will be registered again under the new IP address:

% docker start www

... dns logs ...
2014-10-11T15:29:37.374072 [dnsrest] setting www (83854cf229) as active
2014-10-11T15:29:37.374209 [dnsrest] added * ->
2014-10-11T15:29:37.374286 [dnsrest] added ->

... confirm the ip is correct ...
% docker inspect -f '{{.NetworkSettings.IPAddress}}' www

You can use the DNS server from your containers using:

% docker run -it --name shell --dns --dns-search ubuntu bash
root@e776fff8d971:/# ping foo
PING ( 56(84) bytes of data.
64 bytes from icmp_seq=1 ttl=64 time=0.087 ms
64 bytes from icmp_seq=2 ttl=64 time=0.102 ms
64 bytes from icmp_seq=3 ttl=64 time=0.106 ms   

root@e776fff8d971:/# ping
PING ( 56(84) bytes of data.
64 bytes from icmp_seq=1 ttl=64 time=0.056 ms
64 bytes from icmp_seq=2 ttl=64 time=0.106 ms

... dns logs ...
2014-10-11T15:32:54.874238 [dnsrest] resolved ->
2014-10-11T15:36:40.487780 [dnsrest] resolved ->

The DNS server will also forward any names which do not match, to the resolver you specify (default is This can be disabled by setting the --no-recursion command line option:

root@e776fff8d971:/# ping
PING ( 56(84) bytes of data.
64 bytes from icmp_seq=1 ttl=61 time=33.4 ms
64 bytes from icmp_seq=2 ttl=61 time=31.8 ms
Docker Pull Command
Source Repository