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
windows: start up with loopback dns configured - no route to host #247
Comments
Your config looks good. "bootstrapDns" resolver should be used to resolve the addresses from the links. If you add |
Yes, it's there. I should also mention this is on a Windows host.
|
interesting, I have only linux machines to test. Is 8.8.4.4 reachable with nslookup ( |
I'll try today on a Windows 10 VM, maybe this is only Windows problem |
That's what I'm testing on as well. |
Well that is super odd. This is a fresh install of Windows 10 with nothing else installed, no AV, no well... anything installed. And you had set your DNS to manual config with 127.0.0.1 as the DNS server? If I add a DNS server like 1.1.1.1 as the secondary it works as expected. I really seems like it's trying to default to the configured DNS rather than the bootstrap. |
No, I just started blocky and tried to perform a request against it with nslookup (nslookup google.com 127.0.0.1) and it worked. I'll try again with DNS configuraiton |
I tried again, it worked. After disabling of Ipv6 I could reproduce the behavior. Same error "no such host". Tried on linux with reconfiguration of DNS server -> it works. |
Well that is super weird now, I just tried it again here at my office and it's working just fine with IPv6 enabled. I don't recall disabling IPv6 but it's possible I did. I disabled IPv6 and sure enough, no route to host. |
It looks like golang uses under windows always the system resolver. There is an open proposal in golang which addresses this problem: golang/go#33097 As far I understand. it is not possible to use custom DNS resolver in go binaries in windows |
Updated documentation, added a note that the bootstrapDns works only under Linux/*Nix OSes. Since this is a Go limitation, I'll close this issue and hope this will be fixed in near future by Go devs. |
I'm using a test machine to play around with blocky, which the machine has 127.0.0.1 configured as the DNS server to use blocky. When starting blocky in this scenario, it is unable to download any of the feeds off the get go. I thought that maybe bootstrapDns would be the right setting to enable but it doesn't appear to help. Am I missing something or could blocky use the upstream resolvers to download the feeds on stat up? Thanks!
Current config:
The text was updated successfully, but these errors were encountered: