Skip to main content

Hmm? Ping @github's IP, and ping works
PING 140.82.114.4 (140.82.114.4) 56(84) bytes of data.
64 bytes from 140.82.114.4: icmp_seq=1 ttl=42 time=133 ms
64 bytes from 140.82.114.4: icmp_seq=2 ttl=42 time=133 ms
64 bytes from 140.82.114.4: icmp_seq=3 ttl=42 time=133 ms

Ping the domain, and it just sits there.
ping www.github.com

in reply to dick_turpin

penguin42
penguin42
• •
Your seeing different IPs; here github.com is giving me 140.82.121.4. The 121 is 'fra' - so probably frankfurt; the 114 'iad' so probably Washington. So perhaps they just failed over, or it's distributed.
in reply to dick_turpin

Jon Knight
Jon Knight
• •
It probably has more than one IP address A record attached to that domain name so either the DNS lookup is returning an IP address that is unreachable, or the DNS resolution is taking a long time (or both).
in reply to dick_turpin

dick_turpin
dick_turpin
•
TBF, to me. I took that IP off the web. No idea what a UK or USA IP would be; however, this is 2023, and location should have no impact on name resolution if the Admin is worth anything. @penguin42
@penguin42
in reply to dick_turpin

penguin42
penguin42
• •
No it's explicitly location dependent to route you to a near server; that's pretty common. Try pinging www.google.com from machines in different countries.
⇧