https://blueprints.launchpad.net/ubuntu/+spec/foundations-y-local- resolver has the two outstanding issues to switch NM over to resolved too. These are unblocked now: the new resolved DNS plugin is in upstream master since around September, and NM 1.4 landed in zesty-proposed yesterday. Let's land that first, then backport the DNS plugin and switch it over, then we'll consistently use resolved everywhere and that comment will be much easier to write.
This is also the reason why I didn't do this comment change yet, I think it's better to wait for the above. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1638836 Title: resolv.conf for resolved stub server should have a comment how to see the actual servers Status in network-manager package in Ubuntu: Triaged Status in resolvconf package in Ubuntu: In Progress Bug description: resolv.conf currently just has nameserver 127.0.0.53 with resolved (its local stub resolver). We should have an extra comment on top of that that says # systemd-resolved stub resolver; run "systemd-resolve --status" to see the actual name servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638836/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
