logcli on OSX does not respect VPN DNS

[brokenjacobs]

Describe the bug
When connected over a VPN, on OSX, the logcli binary doesn't use the scutil resolvers configured by the vpn, instead it tries to parse /etc/resolv.conf and use the native go resolver. This is due to the way the go resolver system works on OSX.

To Reproduce
Steps to reproduce the behavior:
Connect with vpn.
use logcli
observe host not found error

Expected behavior
logcli connected to the appropriate server and working

Let's just cut to the resolution here, many go cli tools have suffered the same problem, including kubectl. The solution is to compile cgo support when building for darwin/osx. Here are the relevant kubectl issues:
kubernetes/kubernetes#23130
kubernetes/release#469
and some linked background material:
https://inconshreveable.com/04-30-2014/cross-compiling-golang-programs-with-native-libraries/

[stale]

This issue has been automatically marked as stale because it has not had any activity in the past 30 days. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

[rfratto]

Reopening since the PR to fix is also marked keepalive.

[mattmendick]

Does the dns-heaven tool work to workaround this? Not a good solution for sure, but something that might help ease the pain.

[brokenjacobs]

yes

[slim-bean]

I'm going to close this issue (and the associated PR) with the suggested dns-heaven workaround above. I'm not sure if this is the best solution but we haven't really heard other complaints about this and I don't want to leave it idle forever.

Please feel free to add comments or thumbs up this issue if the workaround doesn't work for you or you have other ideas, thanks!