ResolveError on Ubuntu 20.04 VM

[TheDan64]

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

[sigmaSd]

It looks in /etc/resolv.conf according to the docs
https://crates.io/crates/trust-dns-resolver

[sigmaSd]

Its fixed upstream hickory-dns/resolv-conf#25

[JoshLambda]

The fix upstream still need to be reflected here. It would be solved by updating dependency to crate resolv-conf to version 0.7 in Cargo.toml

[TheLostLambda]

Hey @TheDan64 ! Does the version in PR #201 fix the issue? If so, I can merge that in for you!

[JoshLambda]

@TheLostLambda Thanks! Your PR did fix this issue for me at least.

[gerrywastaken]

@TheLostLambda I'm running into the same issue following the same steps as Op. Given there are also other reports #210 and #212, perhaps this should be reopened?

[gerrywastaken]

Hey everybody bandwhich -d 1.1.1.1 is a workaround so that it doesn't try to read your dns config and get confused.

[TheDan64]

Sorry for the delayed response.

@gerrywastaken 's workaround does work for me w/ the latest version on crates.io.
@TheLostLambda Building from main does work for me now. Thanks! This should maybe receive a new release, though?

[TheLostLambda]

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).

[imsnif]

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.

[gerrywastaken]

@imsnif are you sure it wouldn't be better to migrate to travis-ci.com? Doing a quick search I couldn't see a way to run things on OSX without hosting your own custom runner.

[imsnif]

@imsnif are you sure it wouldn't be better to migrate to travis-ci.com? Doing a quick search I couldn't see a way to run things on OSX without hosting your own custom runner.

No idea - I have done 0 research on this. When I have the time I'll look into this further. Thanks!

[64kramsystem]

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 :)

[virtualritz]

I'm getting this error on Ubuntu 23.04 with bandwhich v0.20.0 installed via cargo. No VM.
I'm connected and I do not have a VPN running.

My resolv.conf looks like this (i.e. it has the trust-ad thing that is mentioned here):

nameserver 127.0.0.53
options edns0 trust-ad
search Speedport_W_724V_09091602_00_012

[cyqsimon]

Moving discussion to #235. See also #275.