Brad House

Obviously the conflicts need to be resolved, but a few other things. 1) I see uses of things like `struct ares_caa_reply**`, but since you have a typedef, there's no need...

> Also, i made the ttl field of ares_uri_reply an unsigned int instead of an int, which isn't strictly related to this PR but I think it was a bug...

> So far this addresses numbers 1 and 2 on your list. I had a question about 4 which i put inline on the code above. I'll also continue working...

Hi @kylebevans sorry for the late reply here, it may be a couple of weeks before I have time to review this. Thanks for doing this though, I'm sure we'll...

I'm pretty sure that would be undefined behavior. c-ares doesn't have any way to update the configuration at this time. I know in my own private use of c-ares I...

Probably. I'm not very much in love with the c-ares API in general. Too many public structs, no way to cancel a single query, no way to reload system config...

Interesting. My guess is c-ares is doing something bad with STAYOPEN if a query needs to switch from udp to tcp due to the result size being too large. I...

You should be registering socket callbacks instead to be notified when descriptors you need to monitor change. Your solution sounds very fragile if you can't handle the file descriptors changing...

is this a regression from a prior version? what version of c-ares is being used?

This would break ABI to expose since the data structure are not opaque. At some point we should figure this out, but it isn't going to be easy unfortunately.