We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Until recently, /etc/resolver/ was not respected by golang's built in DNS resolver. (background on custom resolvers)
/etc/resolver/
This was recently fixed in golang 1.20. See golang/go#12524
/etc/resolver/myhost.com
nameserver 8.8.8.8
evans --host myhost.com -r cli list
evans binaries distributed by the standard methods (brew, etc.) are built with CGO_ENABLED=0. They should respect the /etc/resolver DNS settings.
evans
CGO_ENABLED=0
/etc/resolver
v0.10.9
protoc
I will raise a PR to:
go mod tidy
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Describe the bug
Until recently,
/etc/resolver/
was not respected by golang's built in DNS resolver. (background on custom resolvers)This was recently fixed in golang 1.20. See golang/go#12524
To reproduce
/etc/resolver/myhost.com
with content (can change the ip address to your custom DNS, etc):evans --host myhost.com -r cli list
Expected behavior
evans
binaries distributed by the standard methods (brew, etc.) are built withCGO_ENABLED=0
. They should respect the/etc/resolver
DNS settings.Environment
v0.10.9
protoc
version: N/Aprotoc
plugin version (if you are using): N/AAdditional context
I will raise a PR to:
go mod tidy
for good measureThe text was updated successfully, but these errors were encountered: