marvinsinister/bind repository overview

⁠What is bind

BIND 9 has evolved to be a very flexible, full-featured DNS system. Whatever your application is, BIND 9 probably has the required features. As the first, oldest, and most commonly deployed solution, there are more network engineers who are already familiar with BIND 9 than with any other system.

⁠How to use this image

⁠start a bind instance

The image is configured to work as caching DNS server without forwarder, all you need to do is provide rndc.key named rndc-key.

You can generate one by running:

$ docker run --rm docker.io/marvinsinister/bind rndc-confgen
key "rndc-key" {
        algorithm hmac-sha256;
        secret "***";
};

...

Save it as rndc.key and mount it in /etc/bind/named.conf.d/ folder:

$ docker run --mount type=bind,src=rndc.key,dst=/etc/bind/named.conf.d/rndc.key docker.io/marvinsinister/bind

⁠Defaults

By default bind in this image is configured to listen on port 5353/udp for DNS requests, and on port 5953/tcp for control channel (rndc). Service is running as bind user with uid and gid of 5353. Default named.conf is just including all config from /etc/bind/named.conf.d, where config for default listener and rndc configs are located.

⁠Custom config

To use custom config, just create your custom config and mount it on /etc/bind/named.conf.d:

$ docker run -v /custom/config:/etc/bind/named.conf.d docker.io/marvinsinister/bind

⁠Git repo

https://github.com/marvin-sinister/container-images⁠