public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "René Berber" <rene.berber@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Cygwin unable to resolve hostnames
Date: Wed, 22 Jul 2015 21:50:00 -0000	[thread overview]
Message-ID: <mop2jp$kkn$5@ger.gmane.org> (raw)
In-Reply-To: <CAPohr29Vzd0N8+WsJHpK1tPHjFf+3rtxWUQAyOFqnCdCLZcMcw@mail.gmail.com>

On 7/22/2015 3:53 PM, Matthew Fountain wrote:

> I'm not sure when this started, but recently Cygwin has been unable to
> resolve (certain) hostnames.
>
> Example:
>  wget github.com
> --2015-07-22 15:17:04--  http://github.com/
> Resolving github.com (github.com)... failed: Non-recoverable failure
> in name resolution.
[snip]
> Any ideas?

Cygwin by default uses the same resolution as Windows, that means that
you have something in Cygwin's configuration that affects resolution.

First and most obvious is /etc/resolv.conf; by default I don't think
there is one, but you can create it and Cygwin will use it.

Next would be if you have more than one DNS resolver in your (Windows)
network configuration, this means that any one of them can be used at
any time (literally it should be random)... and by coincidence Cygwin is
using one that doesn't work, the Web browser is using another, and
things change with different tests. Run 'ipconfig -all' and see under
the network adapter what's listed for "DNS Servers".

Also if there is more than one network adapter something similar to the
last paragraph will happen. I would think that Cygwin uses the DNS
servers on the "default" adapter.

Hope this helps.
-- 
René Berber


--
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:[~2015-07-22 21:50 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 [this message]
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
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='mop2jp$kkn$5@ger.gmane.org' \
    --to=rene.berber@gmail.com \
    --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).