Well, oddly enough it was falling through the nameserver list to the
secondary option, and that nameserver was giving bogus data. Though,
why it only affected cURL, I'm still not sure.

On 21 Sep 2005, at 01:15, Daniel Stenberg wrote:

> On Tue, 20 Sep 2005, Michael Morris wrote:
>
>
>> For some reason curl is trying to connect to 1.0.0.0 for any
>> entered domain name
>>
>> $ curl -v www.google.com
>> * About to connect() to www.google.com port 80
>> * Trying 1.0.0.0... ^C
>>
>
> It looks like you have a bad proxy set in an environment variable
> or default config file.
>
> --
> Commercial curl and libcurl Technical Support: http://haxx.se/
> curl.html
>
Received on 2005-09-21