-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 01/22/2016 01:06 PM, Florian Weimer wrote:
On 01/21/2016 11:18 PM, Orion Poplawski wrote:
> PS - There is some other discussion around "mymachines" which seems much
> more problematic. I'd like to just focus on myhostname for now. The
> glibc maintainer has indicated that he wants to wait for mymachines to be
> resolved, but it's almost two months now and I don't see that being
> resolved soon.
I still have philosophical objects to myhostname as well. I find it odd
that at one end, we struggle with DNS name space hijacking, but on another
end, we do basically the same thing:
<
https://github.com/systemd/systemd/issues/2026>
The order in nsswitch.conf does not matter (and neither does any non-DNS
name resolution mechanism) because if we end up having software which
expects that “gateway” resolves to the IP address of the default gateway,
we still have an interoperability problem. And if “gateway” is never
intended for name resolution, why synthesize the name at all?
For what it's worth, nss_myhostname is extremely valuable even without
"gateway". Having the the machine's hostname automatically resolving even
to
DHCP-assigned addresses solves a lot of issues, including some extremely
common ones related to FreeIPA installation.
So if nothing else, I'd really like to see this feature back to being
installed by default.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iEYEARECAAYFAlamMT4ACgkQeiVVYja6o6NuYwCgsByDXdtc2Ok1zwtdgSXOTN01
/RsAnRdCAjMDFD6Vch3kN4Bdo/B7IC9z
=BOZh
-----END PGP SIGNATURE-----