I guess that a .path unit can be setup to parse the private
/run/systemd/netif/state file (or similar), which would then kick off
and feed the DNS entries to resolfconf.
** Also affects: resolvconf (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1689410
Title:
nplan with networkd + resolvconf without resolved, results in no DNS
resolution
Status in ifupdown package in Ubuntu:
New
Status in nplan package in Ubuntu:
New
Status in resolvconf package in Ubuntu:
New
Status in systemd package in Ubuntu:
New
Bug description:
if nplan yaml specifies nameservers which are passed onto networkd,
they will never take effect on systems that do not use systemd-
resolved.
This is because there is no integration between nplan and resolvconf,
either directly; via networkd; via NetworkManager.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1689410/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
