2008/4/30, Yang Tse wrote:

> I'll update this thread when I have further info.

Ok, here it is...

This 'strange' problem was related with DNS configuration issues. As a
matter of fact there is no real problem and everything works as
expected.

When using a c-ares enabled libcurl if for some reason there is no
name server configured at all, and it tries to resolve an unresolvable
host it will properly timeout the query after the configured timeout.
This is the same proper behaviour achieved when the network is down
and trying to resolve an existing host.

A 'funny', but also proper, behaviour can be achieved in tests 507 and
534 when trying to resolve a non-existing host and the configured
nameserver happens to be one that 'resolves' non existing hosts (wow),
such as OpenDNS. If this happens tests 507 and 534 will return a
CURLE_OK 0 errorcode when they were expecting a
CURLE_COULDNT_RESOLVE_HOST 6 errorcode.

-- 
-=[Yang]=-