Out of the box, my LXC containers connect to a running instance of dnsmasq, which is started with the
In my case, I am running a local unbound DNS server that connects to a thing called ncdns which lets me browse .bit domains that are registered via Namecoin.
The two of these conflict. My lxc containers depend on
dnsmasq for DNS, which runs on port 53. At the same time my
unbound server must run on port 53 in order for me to reach .bit domains. (see the comments on this post for the unlikelihood of being able to include a nameserver in resolv.conf using a nonstandard port; I also asked on an IRC channel and basically learned that pointing resolv.conf to a DNS server on a nonstandard port is basically not possible).
So what I need to do is create a combined DNS server that supports LXC's stuff and can also resolve .bit domains, and run THAT on port 53.
It may be assumed that my
unbound server recursively resolves .bit domains, and forwards all other domains to my router, so it can effectively resolve all domains.
Questions are as follows:
1: How do you tell lxc-net NOT to start dnsmasq?
2: I assume
unbound won't just work as the DNS server for my LXC containers without further configuration. How do I configure
unbound so that it does what
dnsmasq does for my lxc containers? (An answer to this question could be either the location of the dnsmasq conf files that it uses when started by lxc-net (which I have not yet found) so that I can attempt to copy that configuration under unbound, or some other documentation that has the same information as the dnsmasq conf files used by lxc-net)