Sometimes github.com resolves to 192.30.253.112 and .113 and today(at least) they don't allow port 22 ssh, so `git push` fails like ssh: connect to host github.com port 22: No route to host
I noticed however that when it resolves to something like 140.82.112.40 (unsure exactly the IP) then ssh works and `git push` succeeds! Valid github IPs can be seen here: https://api.github.com/meta https://www.githubstatus.com/ currently reports all systems operational. So, what ami2do? :) I would need some global way to make sure github.com resolves to the working IP, but unsure how to make this work. Ideally this would be in sys-net's /etc/hosts but this of course doesn't have any effect: github.com still resolves to either of those .112 and .113 IPs. It only works if I put it in the current AppVM's /etc/hosts, of course. How can this be done globally? (Ideally, I would like to even bypass DNS completely, eventually, and only use /etc/hosts (kept up to date manually) but not in this post/thread.) -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/877926d2-5668-4ff5-9864-7eba8e97ca18%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
