This bug was fixed in the package resolvconf - 1.79ubuntu2
---------------
resolvconf (1.79ubuntu2) zesty; urgency=medium
* etc/resolvconf/resolv.conf.d/head: add comment about
'systemd-resolve --status', since systemd-resolved is now in use in all
but the most unusual configurations, and expert users should be given
guidance where to find the actual nameservers for debugging purposes.
LP: #1638836.
-- Steve Langasek <[email protected]> Mon, 28 Nov 2016
15:39:18 -0800
** Changed in: resolvconf (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf 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:
Fix Released
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/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
