[Bug 1638836] Re: resolv.conf for resolved stub server should have a comment how to see the actual servers

[Steve Langasek]

On Fri, Nov 04, 2016 at 11:53:11AM -0000, Thomas Hood wrote:
> What would be far better, though, is to include a text file or manpage
> explaining how name service currently works in Ubuntu.

That doesn't help the problem that /etc/resolv.conf is the file that the
experienced admin expects to contain the nameservers' addresses.

> # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
> # For more info see /usr/share/doc/resolvconf/name-service-in-Ubuntu.txt
> #     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN

The admin is not going to follow documentation links for the thing that
"should" be working the way it always worked and that Ubuntu has broken. 
Documentation is what you look for when you're looking to understand
something new, not to understand why Ubuntu has become buggy and annoying.

This text should go directly in /etc/resolv.conf.

-- 
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