mastermindg/rpi-dns

Bind on Docker on Pi

mastermindg/rpi-dns:latest

• Introduction
  • Contributing
  • Issues
• Getting started
  • Installation
  • Quickstart
  • Command-line arguments
  • Persistence
• Maintenance
  • Upgrading
  • Shell Access

Introduction

Forked from sameersbn/bind - DNS for Raspberry Pi's over Docker

Dockerfile to create a Docker container image for BIND DNS server bundled with the Webmin interface.

BIND is open source software that implements the Domain Name System (DNS) protocols for the Internet. It is a reference implementation of those protocols, but it is also production-grade software, suitable for use in high-volume and high-reliability applications.

Contributing

If you find this image useful here's how you can help:

• Send a pull request with your awesome features and bug fixes
• Help users resolve their issues.
• Support the development of this image with a donation

Issues

Before reporting your issue please try updating Docker to the latest version and check if it resolves the issue. Refer to the Docker installation guide for instructions.

SELinux users should try disabling SELinux using the command setenforce 0 to see if it resolves the issue.

If the above recommendations do not help then report your issue along with the following information:

• Output of the docker version and docker info commands
• The docker run command or docker-compose.yml used to start the image. Mask out the sensitive bits.
• Please state if you are using Boot2Docker, VirtualBox, etc.

Getting started

Installation

Automated builds of the image are available on Dockerhub and is the recommended method of installation.

Note: Builds are also available on Quay.io

docker pull sameersbn/bind:latest

Alternatively you can build the image yourself.

docker build -t sameersbn/bind github.com/sameersbn/docker-bind

Quickstart

Start BIND using:

docker run --name bind -d --restart=always \
  --publish 53:53/udp --publish 10000:10000 \
  --volume /srv/docker/bind:/data \
  sameersbn/bind:latest

Alternatively, you can use the sample docker-compose.yml file to start the container using Docker Compose

When the container is started the Webmin service is also started and is accessible from the web browser at http://localhost:10000. Login to Webmin with the username root and password password. Specify --env ROOT_PASSWORD=secretpassword on the docker run command to set a password of your choosing.

The launch of Webmin can be disabled by adding --env WEBMIN_ENABLED=false to the docker run command. Note that the ROOT_PASSWORD parameter has no effect when the launch of Webmin is disabled.

Read the blog post Deploying a DNS Server using Docker for an example use case.

Command-line arguments

You can customize the launch command of BIND server by specifying arguments to named on the docker run command. For example the following command prints the help menu of named command:

docker run --name bind -it --rm \
  --publish 53:53/udp --publish 10000:10000 \
  --volume /srv/docker/bind:/data \
  sameersbn/bind:latest -h

Persistence

For the BIND to preserve its state across container shutdown and startup you should mount a volume at /data.

The Quickstart command already mounts a volume for persistence.

SELinux users should update the security context of the host mountpoint so that it plays nicely with Docker:

mkdir -p /srv/docker/bind
chcon -Rt svirt_sandbox_file_t /srv/docker/bind

Maintenance

Upgrading

To upgrade to newer releases:

1. Download the updated Docker image:

docker pull sameersbn/bind:latest

2. Stop the currently running image:

docker stop bind

3. Remove the stopped container

docker rm -v bind

4. Start the updated image

docker run -name bind -d \
  [OPTIONS] \
  sameersbn/bind:latest

Shell Access

For debugging and maintenance purposes you may want access the containers shell. If you are using Docker version 1.3.0 or higher you can access a running containers shell by starting bash using docker exec:

docker exec -it bind bash