From: Jun-ya Kato <kato@win6.jp>
To: cygwin@cygwin.com
Subject: Re: Cygwin unable to resolve hostnames
Date: Tue, 15 Mar 2016 01:17:00 -0000 [thread overview]
Message-ID: <20160315.101651.626351874531260985.kato@vanilla.ocn.ne.jp> (raw)
In-Reply-To: <20160314095459.GA20256@calimero.vinschen.de>
> Is anybody here affected by this problem willing to give this a test?
> I can create another Cygwin 2.5.0 test release pretty soon...
I think it's useful workaround for cygwin user under VMware NAT.
I'd like to test it.
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
Subject: Re: Cygwin unable to resolve hostnames
Date: Mon, 14 Mar 2016 10:54:59 +0100
> On Mar 14 09:34, Jun-ya Kato wrote:
>> It also depends on AAAA query againt VMware's DNS proxy server.
>>
>> For more analysis, see vmware community site,
>> https://communities.vmware.com/thread/518949?start=15&tstart=0
>>
>>
>> I think it is not cygwin's bug at all. but any workaround may be
>> implemented againt weak behavior of GetAddrInfoW() API.
>
> As mentioned in the above posting, Cygwin always sets AI_ALL if
> ai_family is PF_UNSPEC and the hints don't specify AI_ADDRCONFIG.
>
> Apparently Winsock's GetAddrInfoW chokes on AI_ALL in certain
> circumstances. On GLibc, AI_ALL is ignored if AI_V4MAPPED is not given,
> but that's not as I observed it on Windows when I added this code
> (back in Vista times, but hey).
>
> There's an easy workaround possible: If GetAddrInfoW returns the
> error code WSANO_RECOVERY (per the above posting), we can retry
> without the AI_ALL flag.
>
> Is anybody here affected by this problem willing to give this a test?
> I can create another Cygwin 2.5.0 test release pretty soon...
>
>
> Thanks,
> Corinna
>
> --
> Corinna Vinschen Please, send mails regarding Cygwin to
> Cygwin Maintainer cygwin AT cygwin DOT com
> Red Hat
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2016-03-15 1:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 20:53 Matthew Fountain
2015-07-22 21:50 ` René Berber
2015-12-11 10:18 ` Carl-Erik Kopseng
2015-12-11 12:12 ` Jan Bruun Andersen
2016-02-11 10:59 ` Carl-Erik Kopseng
2016-02-12 9:06 ` Corinna Vinschen
2016-02-12 13:29 ` Carl-Erik Kopseng
2016-02-16 9:31 ` Brian Inglis
2016-03-13 22:08 ` Carl-Erik Kopseng
2016-03-14 0:34 ` Jun-ya Kato
2016-03-14 9:55 ` Corinna Vinschen
2016-03-15 1:17 ` Jun-ya Kato [this message]
2016-03-15 10:42 ` Corinna Vinschen
2016-03-16 1:57 ` Jun-ya Kato
2016-03-16 10:05 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160315.101651.626351874531260985.kato@vanilla.ocn.ne.jp \
--to=kato@win6.jp \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).