ssh: Could not resolve hostname github.com + STATUS_ACCESS_VIOLATION at eip=68086014

Question

Original question

From a few hours of struggling with installing git on Windows 7. First I installed the GitHub on Windows but not appealed to me. Then I installed the Git-1.9.2-preview20140411 and have started to have problems.

I suppose that there is a conflict by multiple installations. So I uninstalled everything. I decided to try Cygwin.

I acted according to this tutorial: How To install Git client on Windows using Cygwin By Johnathan Mark Smith

I added the generated public key SSH to my account on GittHub by Web browser . I created the first repository (through a browser).

After returning to the cygwin terminal and I typed:

git clone [email protected]:akawalko/ZFExt.git

I received such a result

Cloning into 'ZFExt'...
ssh: Could not resolve hostname github.com: Non-recoverable failure in name resolution
fatal: The remote end hung up unexpectedly

I do not understand this message. I did something wrong?

EDIT 1: To the person who gave me the minus one. In your opinion I shouldn't have asked. Instead, format the hard drive. In this way it would be okay?

Updated question

I started to ask google with less detailed questions and i found it: git and ssh: Could not resolve hostname, ping works. I changed my DNS addresses to open DNS and was able to clone my repo by using ip adres instead domain:

git clone [email protected]:akawalko/ZFExt.git some_git_repo/

Using domain name still not work:

git clone [email protected]:akawalko/ZFExt.git some_git_repo/
Cloning into 'some_git_repo'...
ssh: Could not resolve hostname github.com: Non-recoverable failure in name resolution
fatal: The remote end hung up unexpectedly

Any ideas (other then changing DNS)?

Answer 1

I had this issue inside a VMware Fusion VM. I had to change my network from NAT to Bridged and it started working.

Answer 2

For anyone else having this issue on VMWare Fusion and Windows 10, see this thread: https://communities.vmware.com/thread/518949?start=0&tstart=0

In summary, ssh won't do dns resolution over NAT on Fusion with Windows 10. This is a known bug, but in the meantime, add an entry to your host file to access bitbucket

131.103.20.167 bitbucket.org

Also, as @Jim Redmond pointed out, bitbucket is changing their IP addresses soon (December 15, 2016).

Another, more permanent, option would be to set Google as your DNS provider. Use 8.8.8.8 or 8.8.4.4. Or for ipv6: 2001:4860:4860::8888 or 2001:4860:4860::8844. https://developers.google.com/speed/public-dns/docs/using