It may be some subtle timing issue related to your specific setup. If you can still reproduce the problem, then probably you can record network traces using tcpdump/wireshark for both working and failing cases and see the difference there.
Both resolution ways should produce the same results, and the only difference is that the "new" way using ares_getaddrinfo() lets c-areas to do A and AAAA queries, instead of doing them in in libcurl using the "old" way. Thanks, Dmitry Karpov -----Original Message----- From: curl-library <curl-library-boun...@lists.haxx.se> On Behalf Of Peter Krefting via curl-library Sent: Tuesday, February 14, 2023 4:58 AM To: Dmitry Karpov via curl-library <curl-library@lists.haxx.se> Cc: Peter Krefting <pe...@softwolves.pp.se> Subject: [EXTERNAL] RE: IPv6 issues with ares_getaddrinfo() Hi! Dmitry Karpov on 2023-01-24: > You need to tweak libcurl options or follow the same logic in your > code to match the behavior of the curl application. Yes, indeed. I was hoping it was easier to create a way to reproduce the bug by using command-line curl, instead of trying to extract something from the way our different code modules interact. Because of that I have not been able to create a simple way to reproduce the problems, all I know is that removing #define HAVE_CARES_GETADDRINFO 1 makes things work, but I am nowhere nearer figuring out why. -- \\// Peter - http://www.softwolves.pp.se/ -- Unsubscribe: https://lists.haxx.se/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.html -- Unsubscribe: https://lists.haxx.se/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.html
