Steve McKenna wrote:
> The problem may be associated with domains that dont exist, ie when
> a query should be timed out, but instead hangs.
That is possible. The bug I fixed in libar had to do with a failure to
retransmit queries for which no reply had arrived. This could be caused when
there's low activity due to a flaw in libar prior to version 0.2.12.
>> The libar fixes that went into 0.2.12 might solve your problem. Have
>> you tried compiling without using libar?
> I will switch to using the standard resolver library to see if that
Either that or try upgrading to v0.2.12, which contains fixes to libar that may
resolve this issue for you.
> Can you please tell me what the difference is between using libar
> and the standard resolver library?
Depending on which implementation you have as the "standard" one on your
machine, you may have one that's not thread-safe, and in any case one that
doesn't have a timeout that the caller can easily control. libar provides an
implementation that's both thread-safe and has very fine-grained timeout
control. It also allows a caller to submit a query, but then go off and do
other things and check back later to see if an answer has arrived.