Hey everyone, I ran into a weird problem after updating my Twingate client on my Mac (macOS Sonoma). Before the update, I had a few custom DNS entries set up in the Twingate client for accessing some internal dev tools. It was working perfectly.
Now, after the update to the latest version, it seems like those custom DNS settings are just being ignored. My connections work, but it's using the default DNS instead, so I can't reach those internal resources by their custom names anymore. I'm pretty new to networking stuff, so I'm not sure where to start debugging. Has anyone else seen this? Is there a specific order or file I should check? 😅
Yeah, had a similar thing happen to a colleague last week. Updates can sometimes reset network configurations or change the order of resolution. First thing I'd check is the DNS resolver order - sometimes the update pushes your system DNS ahead of Twingate's.
Run this in Terminal to see your current DNS resolver order:
```
scutil --dns | head -30
```
Look for entries under your active network interface. You might see your custom entries lower in the list, after your ISP's DNS. If that's the case, the Twingate config file might need a manual tweak post-update. It's usually in `~/Library/Application Support/Twingate/`.
Sleep is for the weak
That `scutil --dns` check is definitely the right first move. A similar thing happened to me with a different VPN client last year, and it turned out the update had flipped a `DNSSettingOrder` key in its plist config from `1` to `0`. I'd add that after you check the resolver list, also look at the output of `sudo dnsmasq --test --conf-file=/path/to/your/twingate.conf` if they use dnsmasq under the hood, just to rule out a syntax error introduced by the update. Sometimes the new version expects a slightly different format.
editor is my home
Oh, that's a super helpful first step, thanks for sharing the Terminal command! I'm still getting used to using the command line for network stuff, so having a specific command to run is great.
When you say look for entries under the active interface, do you mean the one labeled with the Twingate network service? Or the main Wi-Fi/Ethernet one? Just want to make sure I'm looking at the right list.
Good question, it can be confusing! You want to look for the main physical interface, like `en0` for Wi-Fi or `en1` for Ethernet. The Twingate virtual interface (usually `utun` something) often just inherits or uses the DNS config from there. So check the resolver list for `en0` first, that's where the order gets jumbled most often after an update. If your custom entries aren't listed there at all, then the client's config file is the next place to check
editor is my home