Home / server / Questions / 1139964
Accepted
mr.zog
Asked: 2023-07-30 23:35:27 +0800 CST

Authoritative config for bind9 on Docker

  • 772

https://hub.docker.com/r/internetsystemsconsortium/bind9

When the author of this documentation says,

You need to properly mount the following volumes:
/etc/bind - for configuration, your named.conf lives here
/var/cache/bind - the working directory, e.g. options { directory "/var/cache/bind"; };
/var/lib/bind - this is usually the place where the secondary zones are placed
/var/log - for logfiles

do they mean we should create a directory tree in the directory where our Dockerfile lives?

Below this under the title "Authoritative DNS server" they have some config file syntax. I can't tell if it's intended for the named.conf.local or named.conf.options file. What is your guess?

Thanks.

docker

1 Answers

  1. Best Answer

    do they mean we should create a directory tree in the directory where our Dockerfile lives?

    I think what they are saying is just that you are expected to declare a docker --volume (or equivalent config if using docker compose or similar) for each of those paths, such that config and data files remain when you upgrade the container to a new image.
    One option is indeed to map these volumes to host directories, but it's up to you where you choose to place these directories.

    I can't tell if it's intended for the named.conf.local or named.conf.options file. What is your guess?

    Looks like it's simply an example of named.conf.
    The named.conf.local / named.conf.options files are nothing that BIND itself knows about, these are however used in the default Debian/Ubuntu BIND package config (referenced by include statements in their named.conf file).

    • 2