[Bug 1638836] Re: resolv.conf for resolved stub server should have a comment how to see the actual servers
Martin Pitt
martin.pitt at ubuntu.com
Fri Nov 4 12:57:15 UTC 2016
Right, the comment would need to be conditional. My original naïve
approach was to add the comment together with the nameserver, such as
printf "# Run systemd-resolve --status blabla\nnameserver 127.0.0.53\n"
| /sbin/resolvconf -a systemd-resolved
so that the comment would only be there when appropriate and would also
be at the appropriate line.
manpage> Not sure if that really helps -- this would also have to
contain a lot of "if"s, like "if you have resolved/unbound/NM's
dnsmasq/etc." and document all of these cases, which is both confusing
and also prone to get out of sync with their respective upstreams.
(FTR, there is nothing Ubuntu specific here, it's the same in Debian and
any other Linux)
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, 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 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/resolvconf/+bug/1638836/+subscriptions
More information about the foundations-bugs
mailing list