I have a fix for resolvconf here, but it's inaccurate for the desktop
because Network Manager is still doing dnsmasq by default. Opening a
task for NM.
** Also affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** Changed in: network-manager (Ubuntu)
Status: New => Triaged
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Canonical Foundations Team
(canonical-foundations)
--
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
