ubuntu/bind9 repository overview

ubuntu/bind9 is a rock for bind9 maintained by Canonical⁠.

BIND 9 provides software for Domain Name System (DNS) management including both defining domain names authoritatively for a given DNS zone, and recursively resolving domain names to their IP addresses.

[Learn more about bind9⁠]

⁠Tags and Architectures

NOTE: These tags follow a specific naming convention that respects the concept of channels⁠.

⁠Get started

This rock's entrypoint is Pebble, a container-optimized init process that enables the orchestration of a collection of local service processes as an organized set.

[Learn more about Pebble⁠]

⁠Inspect

To view the Pebble services⁠ and checks⁠ defined in this rock:

docker run --rm ubuntu/bind9:9.20-25.04_beta plan

docker inspect --format='{{.Config.Entrypoint}} {{.Config.Cmd}}' ubuntu/bind9:9.20-25.04_beta

⁠Run

To run this rock, use any of the usual container runtimes, for example, docker:

docker run --name bind9-container \
    -e TZ=UTC  -p 30053:53/tcp -p 30053:53/udp \
    ubuntu/bind9:9.20-25.04_beta \
    --args <named-args>

Access your Bind9 server at localhost:30053

Additionally, you can use rndc to manage the server:

docker exec bind9-container rndc <command>

A rndc key must have been previously generated either by mounting a volume containing a rndc.key file or by running rndc-confgen with:

docker exec bind9-container rndc-confgen -a
docker restart bind9-container

docker run --name bind9-container \
    -e TZ=UTC -p 30053:53/tcp -p 30053:53/udp \
    ubuntu/bind9:9.20-25.04_beta \
    <named-args>

⁠Get logs

To view the logs of the running container, run:

docker exec bind9-container pebble logs

Or, for a specific service:

docker exec bind9-container pebble logs <service>

docker logs bind9-container

⁠Monitor health checks

Rocks may have predefined health checks that you can list by running:

docker exec bind9-container pebble checks

The overall health of your container can be inspected via:

docker exec bind9-container pebble health

⁠Deploy with Kubernetes

Works with any Kubernetes; if you don't have one, we recommend you install MicroK8s⁠. Then, run microk8s.enable dns storage and snap alias microk8s.kubectl kubectl.

Download bind9-deployment.yml⁠ and set containers.bind9.image in bind9-deployment.yml to your chosen channel tag (e.g. ubuntu/bind9:9.20-25.04_beta), then:

kubectl apply -f bind9-deployment.yml

You will now be able to connect to the bind9 server on http://localhost:30053.

⁠Configuration

⁠Environment variables

⁠Volumes

⁠Ports

⁠Other configuration options

[Report a bug⁠] [Contribute⁠]

Canonical is the provider of this container image. It is the user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within, as well as with Canonical’s IP Policy⁠.