Curl dns resolution name issue on servers with ipv6 #20
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue on servers with ipv6 related to timeouts try to resolve api.zadarma.com on Ipv6, the developer can now set the preference on which ip protocol use for dns resolution.
To avoid breaking things, the default behavior still is CURL_IPRESOLVE_WHATEVER, but some setters has been added to allow change to ipv4 or ipv6 (for future)