Channels
announcements
automation-api
aws
azure
blog-posts
built-with-pulumi
cloudengineering
cloudengineering-support
content-share
contribex
contribute
docs
dotnet
finops
general
getting-started
gitlab
golang
google-cloud
hackathon-03-19-2020
hacktoberfest
install
java
jobs
kubernetes
learn-pulumi-events
linen
localstack
multi-language-hackathon
office-hours
oracle-cloud-infrastructure
package-authoring
pulumi-ai
pulumi-cdk
pulumi-cloud
pulumi-crosscode
pulumi-deployments
pulumi-kubernetes-operator
pulumiverse
python
registry
status
testingtesting123
testingtesting321
typescript
welcome
workshops
yaml
Title
v
victorious-exabyte-70545
10/13/2022, 5:52 PMHi folks, I am having this issue: (Pulumi can't access VPN URLs) https://github.com/pulumi/pulumi/issues/4739. VPN DNS resolution problem on MacOSX. Is anyone else dealing with this. Any suggestions on workarounds?
b
brainy-church-78120
10/13/2022, 6:22 PMcan you pls comment on the issue with your particular situation?
v
victorious-exabyte-70545
10/13/2022, 6:33 PMI am trying to connect to a kubernetes cluster, when connected to the vpn. my kubeconfig has an azure fqdn that is only resolvable from my vnet dns. I have forwards attached to the vnet that allow for vnet resolution. Problem is pulumi uses /etc/resolv.conf which points to my local dns configuration (in this case it is my router).
The issue that I have linked is the same issue that I am having.
This is really an issue with MacOSX and DNS resolution but wondering if people have work arounds. My current work arounds are to add internal fqdns to my hosts file (which is terrible).
Note that tools like ping, curl, etc. correctly resolve the records for my vnet using the forwarder dns servers.
but pulumi cannot.
This is also an issue with terraform and mac osx.
e
echoing-dinner-19531
10/13/2022, 9:21 PMI know Go on macos has some sort of oddities with dns resolution, although I can't recall the specifics I know one of our engineers who probably does know. I'll point this ticket at him.
o
orange-policeman-59119
10/13/2022, 9:33 PMThis is a known issue with Go, unfortunately. I'll update our own issue with a link to this issue:
https://github.com/golang/go/issues/12524
b
brainy-church-78120
10/13/2022, 9:34 PMit's already linked in the issue description
o
orange-policeman-59119
10/13/2022, 9:44 PM@victorious-exabyte-70545 Could you reply to the Go issue as a user of CLI tools on macOS? It would be enough to say that as a developer on macOS, the tools you use written using Go don't work correctly on macOS.
As you noted, it affects every program written in Go unless the program's author takes a costly step to build all macOS programs on macOS using "cgo". That workaround has tradeoffs we don't consider acceptable: as a member of the Go team has said: "cgo is not go" by Dave Cheney. The article linked there lays out how using cgo by default changes a lot more than just how DNS works.