[v2] DNS resolution failing when using vault go binary

[scottillogical]

Reproduced on TP 2.1.2 and 2.2.0 and vault 1.0.0 and 1.7.1. This previously worked on tp v1.

git:(master) ✗ export VAULT_ADDR='http://vault-sandbox-scott.sandbox-scott:8200'
git:(master) ✗ vault status
Error checking seal status: Get "http://vault-sandbox-scott.sandbox-scott:8200/v1/sys/seal-status": dial tcp: lookup vault-sandbox-scott.sandbox-scott on 8.8.8.8:53: no such host
git:(master) ✗ curl http://vault-sandbox-scott.sandbox-scott:8200/v1/sys/seal-status
{"type":"shamir","initialized":true,"sealed":false,"t":3,"n":5,"progress":0,"nonce":"","version":"1.7.0","migration":false,"cluster_name":"vault-cluster-f5d424fe","cluster_id":"16fd5e25-8032-1dbe-76e2-0a1e931296e0","recovery_seal":true,"storage_type":"file"}

Steps to reproduce:

1. Install vault into your namespace via helm helm -n $namespace install --wait --create-namespace vault-$namespace hashicorp/vault
2. boot up telepresence 2 via tp connect (--mapped-namepaces didnt help)
3. Install vault locally and attempt to to connect to the deployed vault with the above steps

[scottillogical]

I resolved this by using a version of vault built with CGO_ENABLED=1

[scottillogical]

reference to underlying vault issue for posterity hashicorp/vault#1159