tecspace/bind9-mikrotik repository overview

To the project

By default, Mikrotik uses the Internet provider's DNS servers, so it is a DNS forwarder. Alternatively, you can specify the public DNS servers of Google & Co.

For security reasons, we have considered setting up our own DNS server that resolves DNS queries independently.

This is how this project was born. Our Docker container is based on Alpine Linux and Bind9 and runs wonderfully on a Mikrotik router.

Environment Variables

The Docker Conainer is already configured and ready to use. However, you can set the following variables to adjust the defaults to your needs.

Here are the variables:

BIND9_CMD_OPTS: All parameters passed to Bind9's startup command.

default: -g -4 -u named

BIND9_CFG_OPTS: All settings in the options block of Bind9 configuration are used.

default: version "hidden";directory "/tmp";listen-on {any;};listen-on-v6 {none;};recursion yes;allow-query {0.0.0.0/0;};dnssec-validation yes ;max-cache-size 64M;

BIND9_STAY_ON: If starting Bind9 is not possible for some reason, the container will shut down by default. If BIND9_STAY_ON=1 is set, the container will continue to run even if starting Bind9 fails. You can log into the container from the Mikrotik shell in order to better analyze the cause.

default: (empty)

Please feel free to send suggestions for improvements or thanks to TecSpace⁠!