Re: "Could not resolve host" for IPv6-only names with curl in 1.18.0

2021-10-26 Thread Brad House via c-ares
Found it, looks like ai_addrlen is being set to sizeof() the wrong structure ... ugh. https://github.com/c-ares/c-ares/commit/71adb3c4170dc47f71c21bf8d95ed7ddd640819e looks like we need a quick 1.18.1... On 10/26/21 5:35 PM, Brad House wrote: Erm, this is really strange.  I mean just using the

Re: "Could not resolve host" for IPv6-only names with curl in 1.18.0

2021-10-26 Thread Brad House via c-ares
Erm, this is really strange.  I mean just using the c-ares ahost() which calls ares_gethostbyname(), I get reasonable results: $ ./ahost -t u production-all-ipv6.easypost.com production-all-ipv6.easypost.com    2607:f0d0:2901:7e::2 production-all-ipv6.easypost.com    2607:f0d0:3803:ca::2 product

"Could not resolve host" for IPv6-only names with curl in 1.18.0

2021-10-26 Thread James Brown via c-ares
Testing an upgrade from 1.17.2 to 1.18.0 and all curl requests to internal names started failing with "Could not resolve host". adig and ahost are both able to resolve the names just fine. It appears that this affects any lookup that only returns IPv6 addresses, and possibly also any lookup that is