Hi,

Senthil Raja Velu wrote:

this messages
> * Trying 10.20.4.19... getaddrinfo(3) failed for bge0:0
suggests you are using curl without ares and threads for name resolving.

this would actually match my own setup:

   curl version: 7.19.4-20090219
   Host setup: x86_64-unknown-linux-gnu
   Install prefix: /opt/curl
   Compiler: gcc
   SSL support: enabled (OpenSSL)
   SSH support: no (--with-libssh2)
   zlib support: enabled
   krb4 support: no (--with-krb4*)
   GSSAPI support: no (--with-gssapi)
   SPNEGO support: no (--with-spnego)
   c-ares support: no (--enable-ares)
   ipv6 support: enabled
   IDN support: enabled
   Build libcurl: Shared=yes, Static=yes
   Built-in manual: enabled
   Verbose errors: enabled (--disable-verbose)
   SSPI support: no (--enable-sspi)
   ca cert bundle: /etc/ssl/certs/ca-certificates.crt
   ca cert path: no
   LDAP support: enabled (OpenLDAP)
   LDAPS support: no (--enable-ldaps)

As I guess the problem to be within Solaris 10 getaddrinfo behaviour, a
small programm is attached.

If it works, there try compiling curl with --enable-ares, and see if
problem persists.

The program:

gcc -o getaddrinfo getaddrinfo.c

execute

./getaddrinfo 127.0.0.1 10.0.53.1 2001:4860:0:1001::68

should give:

resolving 127.0.0.1
         2 127.0.0.1
resolving 10.0.53.1
         2 10.0.53.1
resolving 2001:4860:0:1001::68
         10 2001:4860:0:1001::68

So, please
1) try the attached program and sent the results
2) compile curl with ares, and see if problem persists

Daniel, are you aware of *any* problems using the Curl_resolv functions
to resolve hostnames on Solaris10?

MfG
Markus