net: provide mechanism to force DNS via cgo #11450
Closed
Labels
Milestone
Comments
CL https://golang.org/cl/11584 mentions this issue. |
If we're talking about #10552, then I think an environment variable would be more useful than a compile-time option, because often the people affected will not be the application developers. That said, it's better to ship a correct algorithm, than an incorrect one with an easy workaround. |
@rsc had reservations about an environment variable. My first version of the CL used an environment variable, but it's now a build tag. |
@rsc says:
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We should probably provide a mechanism in Go 1.5 to let users force the use of cgo/libc for DNS resolution. I'm afraid the pure Go solution will have problems for some users, and saying "modifying your nsswitch.conf or resolv.conf to be 'complicated enough'" isn't a great answer.
So, two questions:
/cc @pmarks-net @mikioh @ianlancetaylor @rsc
The text was updated successfully, but these errors were encountered: