On 05/01/16 19:05, Martin Lucina wrote:
On Monday, 21.12.2015 at 15:25, Martin Lucina wrote:
2. "env", "hostname", "net": Hopefully nothing controversial here. I plan
to add a "net.dns{}" to generate resolv.conf and support for NFS mounts in
some form, tentatively as "net.mount{}".
I have now implemented support for configuring the DNS resolver. Excerpt
from the spec should be self-explanatory:
"dns": {
"nameservers": [
<ip-address>,
...
],
"search": [
<domain-suffix>,
...
]
}
You need to define the semantics wrt. to dhcp (which will hopefully be
fixed RSN to capture the resolver info), preferably so that those
semantics are implied by the config format. Does a manual block replace
or augment the resolver given by dhcp (augmentation above or below), or
is the manual block ignored if a dhcp address is successfully retrieved?
To me, it seems easier to minimize complexity by not sticking your hands
into that pile at all, and just let people specify the dns server using
existing methods; and potentially extend the dhcp configuration to
support something like dns=yes/no.
