[systemd-devel] [WIP][RFC][PATCH] networkd: generate resolv.conf

[Djalal Harouni]

On Mon, Jan 06, 2014 at 12:50:23AM +0100, Tom Gundersen wrote:
> Hi Djalal,
> 
> On Mon, Jan 6, 2014 at 12:17 AM, Djalal Harouni <tixxdz at opendz.org> wrote:
> >>  1) nameservers receieved over DHCP
> >>  2) nameservers statically configured in a currently active .network file
> >>  3) nameservers statically configured in the global networkd configuration file
> 
> [...]
> 
> >> So first question: do you agree with adding this functionality?
> >>
> >> Second question: do you agree with the order of precedence I listed above?
> > I'll comment on this:
> >
> > IMO by default try to not be so intrusive
> 
> What in particular do you find intrusive?
IMHO and from a user point of view:
*If there are* static nameservers they should take precedence and avoid
probing DHCP nameservers.

> >  unless *told* so, some configs
> > need their prefered/trusted nameservers.
> 
> With the current patch the admin (or packager) needs to add the
> /etc/resolv.conf -> /run/systemd/network/resolv.conf symlink to get
> any of this at all. If we assume this symlink is in place, I intend to
> still make sure the admin has the full power by having the option of
> statically configuring global and per-NIC nameservers (though these
> will still apply globally due to how resolv.conf works). I'll also add
> an option to opt-out of using the DNS servers received over DHCP.
> 
> Does that sound ok to you?
Hmm, you say to opt-out of using the DHCP nameservers?

IMHO that would be nice to opt-in for DHCP nameservers if there are no
static nameservers or if the networkd config tells this.

For the first part of the /etc/resolv.con symlink that sounds good.

(per-NIC nameservers will be really nice! :-)

Thanks Tom

> Cheers,
> 
> Tom

-- 
Djalal Harouni
http://opendz.org