Networksetup -setdnsservers Ethernet 185.228.168. Networksetup -setdnsservers Ethernet 185.228.168.139 # Older students get an open, but filtered experience: Networksetup -setdnsservers Ethernet 8.8.8.8 Networksetup -setdnsservers Wi-Fi 8.8.8.8 The DNS addresses will change somewhat but I have the script successfully deployed to a couple of test machines. This is the script I cam up with, and testing reveals that it works good, too. The script uses command line tools to talk to the IP address or DNS name of a network. You can have as many commands as you like between the enclosing bracket lines as long. Following are quick outlines of how to setup Jamf Pro Policies and. One other consideration is that if you are running a script in a login policy it will hold up the login process and any other policies until it's completed (depending on the JSS settings) you can mitigate this by passing the script contents to a seperate task (not sure on the terminology but it works). This means you could have one script that was used in multiple login policies each scoped to the appropriate users with the DNS server as a variable for the script as so. You can also use the optional parameter which can be referenced as $4 in the script. If you do it in a policy with login as the trigger $3 will be the username, you can also scope policies to users/groups for login triggers so you don't actiually need the conditionals. Networksetup -setsearchdomains 'Ethernet' your happy with it running only when JAMF is available you can probably approach it something along these lines. Networksetup -setsearchdomains 'Airport' Įcho 'must be MacBook Pro, Mac Mini or iMac' Networksetup -setsearchdomains 'Wi-Fi' You’ll use the -setdnsservers flag, point it at the network service, and then include the DNS IP, this may look like the following: networksetup -setdnsservers (Network Service) (DNS IP) For example, to set a Mac with wi-fi to Google DNS of 8.8.8.8 the syntax would be: networksetup -setdnsservers Wi-Fi 8.8.8.8. Networksetup -setsearchdomains 'Ethernet 2' Networksetup -setsearchdomains 'Ethernet 1' Instead, I used a run once policy that contained a network setup script, scoped to a smart group that contained machines that had the VPN adapter. VMac=`system_profiler SPHardwareDataType | awk '/Model Name:/ '` OS=`sw_vers | grep ProductVersion | cut -c 17-20` Note that I have both 10.6 and 10.7 and had to deal with the differences.Hope it gives you some ideas of what you can do. Here is a script I used for setting up dynamic dns at my site.

Configure dns servers mac jamf script