How would we move forward on changing this?
Cheers,
Trey
Gesendet: Donnerstag, 21. April 2022 um 12:01 Uhr
Von: "Trey Sis"
An: ubuntu-devel-discuss@lists.ubuntu.com
Betreff: Re: Re: Include `::1 localhost` in /etc/hosts
Mostly it is a consistency issue. It seems like all major OS use the convention to have "localhost" resolve to "::1" as well as "127.0.0.1". Even Ubuntu's base Debian uses this convention. Also Arch, Gentoo, OpenWrt, macOS, and Windows.
This way, it is causing issues if people use software on Ubuntu that was crafted for not-Ubuntu, and vice versa. It will also cause masking problems. And thus, it complicates the move towards IPv6. I do understand it might also break some stuff in some cases, but we also can't keep everything forever, especially if the rest of the world has already decided which way to go.
Specific problems most prominently arose probably when NodeJS started to stop reordering DNS replies with preference for IPv4 and now let the OS decide again over DNS sorting order (according to address source and destination selection). This was especially visible when running the automated tests. Wild usage of "localhost" and "127.0.0.1" just decided by gut feeling made this change an uncessarily big effort.
I do agree though that introducing such a change in 22.10 is probably the better option and a good way to iron out issues until making it into the next LTS release.
Looking forward to your comments.
Cheers,
Trey
Gesendet: Donnerstag, 21. April 2022 um 05:14 Uhr
Von: "Richard Laager"
An: ubuntu-devel-discuss@lists.ubuntu.com
Betreff: Re: Include `::1 localhost` in /etc/hosts
On 4/20/22 15:48, Treysis wrote:
> Not having localhost to resolve to ::1 is getting problematic.
Why? Can you elaborate on the issue(s) you're seeing?
I've always assumed the trade-off is as follows:
A) localhost resolves to ::1 (with or without 127.0.0.1 too)
Pro: Things can use IPv6 instead of IPv4 locally.
Pro: It becomes easier to have IPv6-only systems.
Con: If a daemon doesn't listen on ::1, but does on 127.0.0.1,
this change potentially breaks it. If the client(s) use
IPv4 only, then as long as localhost points to both, it
won't break. But if the client prefers IPv6, then it will
break. If the client uses Happy Eyeballs, it will work,
probably with slightly increased initial latency.
B) localhost resolves to only 127.0.0.1
Pro: Daemons that listen only on 127.0.0.1 (because they're old)
or only do so by default (because their default config is old
or the user's config is old) still work.
Con: IPv6 doesn't get exercised as much.
Con: It's harder to have an IPv6-only system.
All that said, at work, my systems have an /etc/hosts that is templated
from Ansible, and my template for Debian and Ubuntu is based on Debian
which points localhost to both 127.0.0.1 and ::1. I've not had any
problems with that.
It's way too late to change this for 22.04, but changing it for 22.10
might be ideal. That would give the maximal time to shake out bugs
before the next LTS.
--
Richard
--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
