Alex Dubov

It is, I assure you. However, there's a caveat: we have a Cisco VPN which insists on advertising an additional resolver; the said resolver is able to resolve AAAA record...

https://danp.net/posts/macos-dns-change-in-go-1-20/ This had started happening relatively recently and I believe it is caused by changes above.

How do I enable both this feature and dns debug so we can see it is used for real?

Tough luck: > % go get nhooyr.io/websocket go package net: confVal.netCgo = false netGo = true go package net: GODEBUG setting forcing use of Go's resolver go package net: hostLookupOrder(proxy.golang.org)...

For reference, curl does this: % curl -v https://proxy.golang.org/nhooyr.io/websocket/@v/list * Host proxy.golang.org:443 was resolved. * IPv6: 2a00:1450:4003:80c::2011 * IPv4: 142.250.184.177 * Trying 142.250.184.177:443... * Trying [2a00:1450:4003:80c::2011]:443... * Connected to proxy.golang.org...

curl gets stuck when forced to use ipv6. It may be that despite underlying adapter has ipv6 disabled, the Cisco vpn client pretends it's got an ipv6 address on the...

The address is of course correct, it's the action of resolving the AAAA and sticking to it rather than resolving A is incorrect. :-)

The problem only happens with VPN enabled, I mentioned it before. The VPN in question is Cisco secure client, aka AnyConnect. I'm working with people who manage the Cisco VPN...

Interestingly enough, this need not be a bazel specific thing. Rather, vscode-go could be made a somewhat more flexible: 1. vscode-go could add an ability to run a command via...

On my side, I've got a bazel rule + go helper binary. The helper binary diffs and edits the "launch.json" file in the ".vscode" dir under the workspace it's working...