Tuesday, October 30, 2012

Github.com won't reliably resolve when pulling/pushing

It started a couple months ago, it was confusing at first, I thought maybe my remote address was screwed up, or I had the wrong public key on github... but it just seems really unreliable.  The message looks like this a lot of the time:
[nak@arch Guru]$ git pull origin development
ssh: Could not resolve hostname github.com: Name or service not known
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

 Then I press up-arrow, enter... over and over again until I'm able to get a connection, and then it works fine...

I figured I'd write about this in case others are googling around, you're not alone, but I don't know the solution yet.  Maybe I'll do a wireshark session to see if I can dissect anything.

Until next time,
Eternally Confused,
Naked Proof~

2 comments:

  1. I am seeing the same from a simple 'git push' command. My solution is the same too. Just try again.

    I saw very similar issues a few weeks ago, but then GitHub admitted to being the victim of a DDoS. Currently, they are not stating anything like that on their blog.

    So, it is simply an intermittent DNS error with the root cause unknown I guess.

    ReplyDelete
    Replies
    1. Thank you very much for a response :)
      It's nice to know I'm not alone.
      Are you using DNS caching? I use pdnsd. I'm also on Arch Linux. Maybe the issue is with something there?

      Delete