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. From: Carl-Erik Kopseng <carle...@gmail.com> Subject: Re: Cygwin unable to resolve hostnames Date: Sun, 13 Mar 2016 23:07:36 +0100 > Just a follow up for anyone else experiencing this. I fixed the DNS > issues by directly specifying a DNS server in the IPV4 settings for my > network adapter in the Windows VM. I used Google's public DNS server > (8.8.8.8) and it worked instantly. > > The cue to check out DNSSEC was a dead-end as the hostname was just an > example. 90% of lookups failed, and the state of the net isn't that > bad :-) > > -- > regards > > Carl-Erik Kopseng > > -- > 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 -- 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
