Deep Dive: Resolving DNS Issues with GitHub and Understanding SSH vs HTTPS

Ever tried pushing your code to GitHub, only to be stopped by a timeout error that makes zero sense? That's exactly what happened to me — and what started as a frustrating blocker turned into a genuinely useful deep dive into DNS, network routing, and Git's connection methods. 🚀 Let me walk you through every step. The Problem: GitHub, You're Killing Me 😩 Everything was going fine until I ran a routine push: git push origin feat/add-tests Instead of the usual success, I got: fatal: unable to access 'https://github.com/your-username/your-repo.git/': Failed to connect to github.com port 443 after 75079 ms: Couldn't connect to server 75 seconds of waiting, then nothing. Time to dig in. 🔍 Step 1: Is GitHub Actually Down? 🌐 Before blaming my own setup, I checked whether GitHub was reachable at all: curl -s -o /dev/null -w "%{http_code}" https://github.com The response? 000 A 000 status code from curl means the request never even got a response — no HTTP handshake, no connection, nothing. Git