From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Cygwin unable to resolve hostnames
Date: Tue, 16 Feb 2016 09:31:00 -0000 [thread overview]
Message-ID: <loom.20160216T094912-392@post.gmane.org> (raw)
In-Reply-To: <CAA05WiaqKoaRuxTCYmrqOquSPGVO+jO0gLLVhcX1L7N0Tr+hLg@mail.gmail.com>
Carl-Erik Kopseng <carlerik <at> gmail.com> writes:
>>> ssh: Could not resolve hostname timbuktu.kopseng.no: Non-recoverable
>>> failure in name resolution
>> I don't think this is a generic Cygwin problem. I can resolve the
>> hostname just fine:
>> $ uname -svr
>> CYGWIN_NT-10.0 2.4.1(0.293/5/3) 2016-01-24 11:26
>> $ ssh timbuktu.kopseng.no
>> The authenticity of host 'timbuktu.kopseng.no (51.175.197.68)' can't be
established.
>> RSA key fingerprint is SHA256:ddcghrb6BI6+TVDKDE3Yf+U43v9EL6u7HsNw7Hec+y8.
>> Are you sure you want to continue connecting (yes/no)? no
>> Host key verification failed.
> I think it has to do with how Cygwin interfaces with VMs. Perhaps it
> has something to do with network tunnelling or something related to
> how ip and DNS works when being NAT'ed through VMWare Fusion.
>
> I am running the Windows 8 VM on VMWare Fusion on OS X 10.11.3
Could it be lack of support for DNSSEC as your domain shows:
$ whois kopseng.no
% Kopibeskyttet, se http://www.norid.no/domenenavnbaser/whois/kopirett.html
% Rights restricted by copyright. See
http://www.norid.no/domenenavnbaser/whois/kopirett.en.html
Domain Information
NORID Handle...............: KOP444D-NORID
Domain Name................: kopseng.no
Domain Holder Handle.......: CK1990P-NORID
Registrar Handle...........: REG42-NORID
Tech-c Handle..............: DH38R-NORID
Name Server Handle.........: NSHY11H-NORID
Name Server Handle.........: NSHY46H-NORID
Name Server Handle.........: NSHY81H-NORID
DNSSEC.....................: Signed
DS Key Tag 1...........: 42355
Algorithm 1...........: 8
Digest Type 1...........: 2
Digest 1...........:
8065b555e0009918e7aba49191e6409481afc702f028c0ff20f1bf27e847e21b
http://dnssec-debugger.verisignlabs.com/timbuktu.kopseng.no shows no issues
with setup.
VMware KB search shows no DNSSEC hits on Fusion, bunch on ESX.
Might want to start with
https://communities.vmware.com/message/1454999#1454999 and the rest of that
thread.
You can browse from there to more generic natd, dhcpd, and net config and
diag info or RTFM.
--
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-02-16 9:31 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 [this message]
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=loom.20160216T094912-392@post.gmane.org \
--to=brian.inglis@systematicsw.ab.ca \
--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).