Comment 11 for bug 1741277
Revision history for this message
| Steve Langasek (vorlon) wrote Re: [Bug 1741277] Re: Not all platforms running cloud-init end up with the system hostname resolveable by default | #11 |
On Tue, Apr 24, 2018 at 05:50:13PM -0000, Jeremy Bicha wrote:
> > The only case where nss-myhostname actually makes sense is if you have
> a read-only /etc, which is not true here.
> I disagree. It is annoying that system administrators need to change
> both /etc/hostname and /etc/hosts instead of being able to change just
> one place: /etc/hostname (or use hostnamectl).
hostnamectl should manage both /etc/hostname and /etc/hosts on Ubuntu. I
am fairly certain that it did in the past.
I think that, aside from users who would use gnome-control-
hostnamectl anyway, changing a hostname is a very infrequent operation and
any admins who are doing this are not going to be troubled by editing
/etc/hosts in addition to /etc/hostname.
I don't like increasing the number of moving parts involved in host
resolution. We pay a cost for each additional nss module that we have to
fall through when searching, and I am not at all convinced that this module
is worth it.
> On recent standard Ubuntu, systemd-resolved handles this. Otherwise,
> libnss-myhostname is what the systemd documentation recommends.
We don't take upstream documentation as gospel when it comes to questions of
how we integrate Ubuntu.