public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jun-ya Kato <kato@win6.jp>
To: cygwin@cygwin.com
Subject: Re: Cygwin unable to resolve hostnames
Date: Mon, 14 Mar 2016 00:34:00 -0000	[thread overview]
Message-ID: <20160314.093450.1409197428128437086.kato@vanilla.ocn.ne.jp> (raw)
In-Reply-To: <CAA05WiY_gwrX=aX2FqzLF0ZeJ4zf0ipNRshCXxOvp+h9MmbENQ@mail.gmail.com>

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 <carlerik@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

  reply	other threads:[~2016-03-14  0:34 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 [this message]
2016-03-14  9:55                   ` Corinna Vinschen
2016-03-15  1:17                     ` Jun-ya Kato
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=20160314.093450.1409197428128437086.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).