Skip to main content

Mac OS X DNS Resolver.

Had an interesting problem today with a Mac OS X 10.7.5 end user working with the Apple built-in Cisco IPSEC VPN client. The end user was using a VPN profile that has split tunneling enabled.

Internal servers could not be reached via their DNS address (ip address did work). The vpn interface was getting the correct DNS settings, the Ethernet interface and WiFi interface were only getting the end users home internet connection DNS settings.

Unfortunately the VPN DNS isn't overriding the ISP's. Doesn't matter whether I change the order of services either.

Manually added the DNS to the interfaces and it works as expected but doing it that way means the end user won't be able to resolve anything when not connected to the VPN.

This is a workaround... real quick one, haven't researched it yet. Will update with more details when I have time.

Popular posts from this blog

Mac OS X "SOE" Day 7

Page Redirection> continued from day 6...

In summary, here is my method for creating a Mac OS X 10.7.3 Standard Operating Environment "SOE" Image.


Overview The goal is to create a "MASTER" non-booted SOE that can be used with multiple models and it multiple sites with different local requirements.

My intention is to use this "MASTER" image in a manual restore procedure due to the fact netboot facilities cannot be made available to all the sites I support however the DMG files are netboot compatible.

RequirementsLion Recovery Disk Assistant v1.0"TARGET" workstation. A compatible workstation that will be used to install Mac OS X 10.7.3 and capture a DMG image(s)."ADMIN" workstation. A workstation with Disk Utility that you will use to capture your DMG image(s).External storage such as a USB HARD DISK. SetupDownloaded the Lion Recovery Disk Assistant v1.0 and followed the instructions to setup an external Recovery D…

Mac OS X "SOE" Day 6

Page Redirection> continued from day 5...

Continuing on from the "firstboot" phase setup we need to script our "localiser" options.

I previously set my build phase to autologin and run the firstboot script, the localiser phase essentially sits there and waits for you to run it.

In my case I have an applescript GUI wrapper that requests some info to use in the localisation. I request a TAG number which is an organisational internal number and I also request a user name that will be set as the OWNER.

NOTE : I ordered these specifically...not just because it makes sense logically but also technically. For example, setting the Language actually zaps a plist file (.GlobalPreferences) which you need to write to for Locale and Country info.

This stuff is going to be totally dependant on your environment, as an example here is what I do.

So what's the minimum we need in the "localiser" phase? Depends on how many sites you support, I support over 50 si…