On Tue, 2014-07-15 at 17:17 +0200, Lennart Poettering wrote: > On Mon, 14.07.14 15:38, Dan Williams (d...@redhat.com) wrote: > > > But that brings up another question; I don't think systemd-networkd is > > currently capable of ensuring a machine is completely configured when RA > > is enabled, because it doesn't handle RDNSS and DNSSD options from the > > RA response. The kernel can't handle those, because those require > > writing to /etc/resolv.conf (or a caching nameserver), which the kernel > > obviously doesn't do. But neither does systemd-networkd. > > systemd-resolved subscribes to networkd state and writes out those > files. It's simply a matter of making networkd pass the RDNSS/DNSSL > records to resolved, too.
Will resolved grow an interface that other services can use to push that information down to it, in addition to the existing approach of listening to networkd events in /run/systemd/netif and then parsing systemd network config/lease files? Dan _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
