On Wed, 9 Sep 2026 11:17:16 +0200 Vincent Lefevre <[email protected]> wrote:
> On 2026-09-09 06:29:27 +0200, [email protected] wrote: > > Given the available portable interfaces, they can only try. > > Traditionally, the sequence DNS resolution then socket connect > > is something that happens in application space (although most > > of the time wrapped in library). So the best it can do when > > DNS yields several entries (some A, some AAAA) is to try them > > all and pick one that works. > > The issue is more that applications hide errors from DNS requests, > giving a misleading error message saying that the IPv6 connection > failed though the real error was IPv4 resolving. I already had > this issue with postfix (due to a bug that lead to an obsolete > /etc/resolv.conf file in postfix chroot): > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964769 > > Error messages should be accurate to that the users can find the > cause of failures. > You're living in the past. These days it's 'Oops, something went wrong'. -- Joe
