Making unbound authoritative

[karolyi]

Hey,

I'm working on setting this container up on my server, while the server itself is intended to be a secondary to certain zones.

That involves using unbound to serve authoritative answers to certain zones I set up in its configuration, and forwarding port 53 (TCP/UDP) to unbound:553 so it can answer queries from the outside.

The first real issue I faced is, unbound only listens on 127.0.0.1 per its config you always overwrite on startup. Upon changing that to ::@553 and 0.0.0.0:553, it started responding to queries.

Would you accept a PR to convert this container to a thing that can act as an authoritative DNS, while responding to DNSCrypt locally too? It will probably involve a bit of work, but still better than using another, unbound-only container that I can configure better. Also, that way I could avoid running unbound twice, just for the sake the setup work as to suit my needs.

[jedisct1]

As long as this is optional (the current behavior is not changed by default), and that everything is properly documented, sure!

[karolyi]

Disclaimer: I'm not a docker expert but can figure it out. I'm gonna come up with something in the near future, which will need your input.