Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

nslookup raw.githubusercontent.com return 0.0.0.0 #5255

Closed
nodew opened this issue May 23, 2020 · 4 comments
Closed

nslookup raw.githubusercontent.com return 0.0.0.0 #5255

nodew opened this issue May 23, 2020 · 4 comments

Comments

@nodew
Copy link

nodew commented May 23, 2020

I could't fetch content from raw.githubusercontent.com, after my investigation, the nslookup returned 0.0.0.0, which is weird.

$ nslookup raw.githubusercontent.com
Server:         192.168.0.1
Address:        192.168.0.1#53

Non-authoritative answer:
Name:   raw.githubusercontent.com
Address: 0.0.0.0
Name:   raw.githubusercontent.com
Address: ::

meanwhile, nslookup github.map.fastly.net works fine.

$ nslookup github.map.fastly.net
Server:         192.168.0.1
Address:        192.168.0.1#53

Non-authoritative answer:
Name:   github.map.fastly.net
Address: 151.101.76.133
@karuboniru
Copy link

karuboniru commented May 29, 2020

If you are in mainland China(seems to be true from the Chinese characters in your bio), that is totally normal, blame GFW instead.

And doing nslookup raw.githubusercontent.com in the windows side should return the same ip. This also suggests that the problem is from the network/DNS itself but not WSL.

Use a proxy to solve this.

For sure you can make raw.githubusercontent.com accessible by a hosts file or a clean DNS, but that will be incredibly slow. I won't suggest that.

@nodew
Copy link
Author

nodew commented Jun 1, 2020

nslookup in windows side work well for me, since I'm already connected to an vpn.

@karuboniru
Copy link

nslookup in windows side work well for me, since I'm already connected to an vpn.

Ok, your problem is that WSL will not access the network through VPN which is set for windows, and it not easy to make a WSL program to use Windows's VPN (I mean IPSec or P2TP..)

Maybe what you need is proxy software like shadowsocks or V2ray and make them listen on certain local port. Then you can tell Linux programs to use the proxy.

@nodew
Copy link
Author

nodew commented Jun 1, 2020

Ok, it looks like a DNS cache issue. After reset the instance, it works now.

@nodew nodew closed this as completed Jun 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants