that's one way to work around it, although glibc is not necessarily the only thing that might do pipelined TCP dns lookups to the local stub resolver (though I have no examples of anything else that does). It certainly should fix/workaround this for Ubuntu installs using the default systemd-resolved setup and only having issues with getaddrinfo() failures.
I still plan to fix systemd's stub resolver to correctly respond to pipelined TCP dns queries.
> Also is this then just not a simple cherrypick of: /github. com/systemd/ systemd/ commit/ 93158c77bc69fde 7cf5cff73361763 1c1e566fe8
>
> https:/
that's one way to work around it, although glibc is not necessarily the only thing that might do pipelined TCP dns lookups to the local stub resolver (though I have no examples of anything else that does). It certainly should fix/workaround this for Ubuntu installs using the default systemd-resolved setup and only having issues with getaddrinfo() failures.
I still plan to fix systemd's stub resolver to correctly respond to pipelined TCP dns queries.