


You can check it in Network Preferences → Advanced → DNS tab. I found a workaround: your VPN DNS will still be ignored, and only 3G-dongle DNS will be used, but just adding your VPN DNS to the list under 3G interface does the trick… The main problem is that 3G connectivity manager overwrites configuration everytime you click connect, and you need connectivity manager to enable Radio on the 3G dongle… so I mixed both solutions in one:Ĭonnect to your VPN and write down your DNS (I have 2 on the list). > set State:/Network/Service/forticlientsslvpn/DNS

This is how it looked on my machine: > get State:/Network/Service/forticlientsslvpn/DNS To check each of them run: (until you find the problematic one) > get key_name SubKey = State:/Network/Service/forticlientsslvpn/DNS This will show you a list of all DNS configs, that will look something like: subKey = State:/Network/Global/DNS Even when FortiClient was disconnected - it's DNS still appeared in the scutil. I had the same problem on my Mac, and after fixing it I have figured out that it was caused by FortiClient (VPN client). So far I have not found a way of doing this. In order to fix my problem with the broken DNS lookups when dialing in via VPN over modem I need to change the order of the resolvers. I assume ping runs into the 5 second timeout of the mdns resolver. ping takes 5 seconds to return "Unkown host", hostgets back immediately. From the response times of the commands (using the non-existing hostname ) I infer that ping uses the first resolver chain, where as host uses the scoped query configuration. This time, ppp1 is the VPN connection and ppp0 is the UMTS connection. As you can see, two servers are connected and they answer correctly on the command line and in applications. The ppp0 connection is the VPN connection. Reach : Reachable,Directly Reachable Address There is a notable difference in the lookup order: connecting using WLAN: Using scutil -dns I dumped the DNS configuration when connecting via WLAN vs. Command line tools like host name will correctly resolve the IP address, ping name will not resolve. However, when I use a dial-up connection (Huawei HSDPA USB Stick) host names are not correctly resolved in applications (e.g. Everything works great when establishing the VPN connection via LAN or WLAN. I am using a MacBook with Mac OS X 10.8.2 and connect to my company's network via VPN.
