bandwhich: ResolveError on Ubuntu 20.04 VM
Installed via cargo install bandwhich
Error: Could not initialize the DNS resolver. Are you offline?
Reason: ResolveError { inner: Custom { kind: Other, error: "Error parsing resolv.conf: InvalidOption(17)" }
io error }
Not sure which resolv.conf it’s looking for since it doesn’t print the full path and I see multiple in a variety of locations. I’ve also never manually modified a resolv.conf file so no clue why it’d fail to parse
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 7
- Comments: 15 (2 by maintainers)
Doesn’t happen on VM only like the title suggests 😃 I’m having this problem (which I can workaround via
-d 1.1.1.1) on a physical machine 😃Hey everybody
bandwhich -d 1.1.1.1is a workaround so that it doesn’t try to read your dns config and get confused.No idea - I have done 0 research on this. When I have the time I’ll look into this further. Thanks!
Hey, thanks for the poke and my apologies for being absent. There’s some non-trivial stuff that needs to be done around the repo (some of which needs to be done before the release, eg. migrating to Github actions because Travis is no longer a thing).
I hope to be able to get this done by the end of the month, but I can’t make any promises. Thanks for your patience.
Heya! Sorry I’ve been a bit tied up recently! I agree that a bug-fix release is probably in order! Unfortunately, I’m slightly unfamiliar with how we publish releases, so I might poke @imsnif for a bit of help!
Hopefully pushing out the new version should resolve things 😃 I’ll reopen this until that’s pushed out (hopefully quite soon).
@TheLostLambda Thanks! Your PR did fix this issue for me at least.
Hey @TheDan64 ! Does the version in PR #201 fix the issue? If so, I can merge that in for you!
Its fixed upstream https://github.com/tailhook/resolv-conf/issues/25