3 ms·
The "typical" practice is to use an "up"/"down" scripts to modify the DNS servers when the VPN link goes up/down. If you just want to use your GCP dnsmasq inst
by jlgaddis 10y ago
The "typical" practice is to use an "up"/"down" scripts to modify the DNS servers when the VPN link goes up/down.
If you just want to use your GCP dnsmasq instance for the .internal top-level domain (not all DNS queries), then you'd want to run a resolver locally that you can configure to selectively forward queries.
This is pretty easy on Linux but I've never attempted it on MacOS. I realize it's probably not ideal but perhaps you can install dnsmasq or unbound on MacOS via homebrew or Macports?
- lobster_johnson 10y agoThe idea is to avoid any unnecessary client-side configuration aside from the connection itself. Adding a resolver on macOS is easy enough (just create a file /etc/resolver/internal for .internal, containing the IP of the DNS server), but the nice thing about OpenVPN is that you get the DNS config automatically.