Aha, but then I suspect that the problem is not in libcurl. libcurl is then simply built to use getaddrinfo() for resolving names. I don't see what we can do to make that misbehave this way!

Is this problem only seen in (lib)curl?

---
** [bugs:#1346] resolver error**
**Status:** open
**Labels:** dns 
**Created:** Mon Mar 17, 2014 03:40 PM UTC by Christian Hesse
**Last Updated:** Mon Mar 17, 2014 03:53 PM UTC
**Owner:** Daniel Stenberg
libcurl has a resolver bug that requires some conditions to trigger:
* libcurl tries to resolv A and AAAA records
* DNS response is too long to fit into a UDP packet
What happens:
* libcurl sends two DNS UDP requests, one for A record, one for AAAA record
* libcurl receives one truncated UDP response
* libcurl sends TCP request
* libcurl receives TCP response
* libcurl sends TCP reset, ignoring the response
Everything works just fine when querying only A record (give option -4).
A capture demonstrating the problem is attached.
---
Sent from sourceforge.net because curl-tracker@cool.haxx.se is subscribed to https://sourceforge.net/p/curl/bugs/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/curl/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.