I try to use propellor to deploy a secondary DNS server.
In your configuration, I see nothing to change the listen-on { 127.0.0.1; }; option, did I miss something?
Also, in Dns.secondaryFor, I do not know how to set confLines to something else, should I use this function and peel the result until I can change this or shoud I add a Dns.secondaryFor' version with an extra argument?
By the way, is it really advisable to use a "minimal config" instead of a full clone?
Thanks!
For the moment I use:
namedOptions :: Property DebianLike namedOptions = File.hasContent "/etc/bind/named.conf.options" namedOptionsStanza `onChange` Service.reloaded "bind9" where namedOptionsStanza = [ "// automatically generated by propellor" , "options {" , "\tdirectory \"/var/cache/bind\";" , "\tdnssec-validation auto;" , "\tlisten-on-v6 { any; };" , "\tlisten-on { any; };" , "\tallow-query { any; };" , "\tallow-recursion { localhost; };" , "\tallow-transfer { none; };" , "\tallow-notify { none; };" , "};" ]At least on Debian, bind seems to come configured to listen on all interfaces by default, so I have not messed with listen-on settings at all.
confLines seems to have been included in NamedConf to allow for specifying additional lines, but there does not seem to be an interface to set it. Versions of the 3 dns properties with an additional (NamedConf -> NamedConf) parameter woulld be one way; I'd take such a patch.
As to a minimal config vs a full clone, it's up to you. With a full clone you can easily modify all of propellor's properties to quicklly deal with issues like this.. but then you might have to maintain your patches if you don't get them accepted into propellor.
It might be a configuration from my server provider, maybe I should do a clean install
If not using a full clone, I also have problem because I cannot use things like Utility.Units.