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.
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
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
anddocker info
commands - The
docker run
command ordocker-compose.yml
used to start the image. Mask out the sensitive bits. - Please state if you are using Boot2Docker, VirtualBox, etc.
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:9.16.1-20200524
Alternatively you can build the image yourself.
docker build -t sameersbn/bind github.com/sameersbn/docker-bind
Start BIND using:
docker run --name bind -d --restart=always \
--publish 53:53/tcp --publish 53:53/udp --publish 10000:10000/tcp \
--volume /srv/docker/bind:/data \
sameersbn/bind:9.16.1-20200524
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 https://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.
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/tcp --publish 53:53/udp --publish 10000:10000/tcp \
--volume /srv/docker/bind:/data \
sameersbn/bind:9.16.1-20200524 -h
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
If you need to run Webmin behind a reverse-proxy such as Nginx, you can tweak the following environment variables:
-
WEBMIN_INIT_SSL_ENABLED
: If Webmin should be served via SSL or not. Defaults totrue
. If you do the SSL termination at an earlier stage, set this to false. -
WEBMIN_INIT_REDIRECT_PORT
: The port Webmin is served from. Set this to your reverse proxy port, such as443
. Defaults to10000
. -
WEBMIN_INIT_REFERERS
: Sets the allowed referrers to Webmin. Set this to your domain name of the reverse proxy. Example:mywebmin.example.com
. Defaults to empty (no referrer).
To upgrade to newer releases:
- Download the updated Docker image:
docker pull sameersbn/bind:9.16.1-20200524
- Stop the currently running image:
docker stop bind
- Remove the stopped container
docker rm -v bind
- Start the updated image
docker run -name bind -d \
[OPTIONS] \
sameersbn/bind:9.16.1-20200524
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