I using L2TP VPNs to remote in to both home and work, both of which run on Windows Server/AD for DNS. The VPN connects fine and I pick up a DHCP address, but in both cases the search domain doesn’t get configured by DHCP. I’ve tried manually configuring it for each VPN connection but it still doesn’t take effect.
I’ve enabled the “Send all traffic over the VPN” option for both connections, and using FQDNs works fine. DNS is working in basic terms, it’s just the search domain that seems to be broken.
Has anyone run in to this/know a solution? I’m running macOS 10.12.2.
How is the search domain being set? If its through DNS on Windows server, I believe it needs to use Option 119 which will require setting the DNS suffixes as hex. These two links describe it as best as I can tell:
It’s set by option 15 currently. My DHCP servers are running 2012 R2, and I can create option 119, but what’s odd is that option 15 alone works fine for local clients, including Macs.
It’s only when I’m connected via the VPN (hosted on another Windows server) that Mac clients don’t pick up the suffix via DHCP. And I find it strange that even setting it manually on the Mac client, within the VPN connection options, still doesn’t work.
I’ll see if adding 119 helps across the VPN though, thank you for your help.