If the A and AAAA queries have equal transaction IDs, the initial AAAA response is not recognized as valid, resulting in timeouts and retransmits.
This bug is distinct from bug 19691 in the sense that it is possible to fix it without reworking the buffer management.
Patch posted: https://sourceware.org/pipermail/libc-alpha/2020-September/117547.html
The master branch has been updated by Florian Weimer <fw@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=f1f00c072138af90ae6da180f260111f09afe7a3 commit f1f00c072138af90ae6da180f260111f09afe7a3 Author: Florian Weimer <fweimer@redhat.com> Date: Wed Oct 14 10:54:39 2020 +0200 resolv: Handle transaction ID collisions in parallel queries (bug 26600) If the transaction IDs are equal, the old check attributed both responses to the first query, not recognizing the second response. This fixes bug 26600.
Fixed for glibc 2.33.
The release/2.32/master branch has been updated by Florian Weimer <fw@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=2dfa659a66f20facc4082207884c20e986ddecee commit 2dfa659a66f20facc4082207884c20e986ddecee Author: Florian Weimer <fweimer@redhat.com> Date: Wed Oct 14 10:54:39 2020 +0200 resolv: Handle transaction ID collisions in parallel queries (bug 26600) If the transaction IDs are equal, the old check attributed both responses to the first query, not recognizing the second response. This fixes bug 26600. (cherry picked from commit f1f00c072138af90ae6da180f260111f09afe7a3)