> On Mon, Jun 06, 2016 at 03:17:51PM +0100, Robie Basak wrote:
>
> Unless the above can be fixed somehow, and I very much doubt resolved
> will grow a DNS server any time soon, the switch to resolved mostly
> feels like a regression over the existing resolvconf+dnsmasq setup we've
> got right now and which in my experience at least, has been working
> pretty well for us.
>
I have in the past tried to drop all config files from /etc.
Dropping /etc/nsswitch.conf is trivial. Apart from libc and shadow
very little else parses that, so that has minimal breakage so things
that do call into libc end up doing the right thing.
Droping /etc/resolv.conf is hard, and in essence a bunch of stuff
parses and uses it, for right and wrong reasons (e.g. even when doing
shared linking with glibc and having it available).
In those cases, things do go wrong. If there is no split routing,
everything is fine and the change is mostly harmless. With split
routing things will break.
Ideally I would like to still see 127.0.0.1 specified in resolf.conf,
and I'll be fine with that being implemented on top systemd-resolvd
api, I don't think that would be hard, however It seems to me like a
re-implementation of resolvconf+dnsmasq solution.
I have heard before that it was requested as desirable to have
plaintext view of the dns config..... can somebody point out how can I
get dns info out of current stable resolvconf+dnsmasq? E.g. what are
my current dns servers, default, per- interface, etc? I guess i'm a
dnsmasq n00b.
--
Regards,
Dimitri.
--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
