Microsoft Intune – Add additional DNS Client Servers across the managed devices

I recently wrote a blog post about adding DNS Client via GPO, highlighting which methods work and which don’t. If you’re interested, you can read more about it on – GPO – PowerShell – Intune – Add additional DNS Client Servers across the enterprise | AskAresh. As promised, here are the steps for performing the same task in Microsoft Intune for all of your managed devices.

Note – The best method of assigning the DNS Servers is through the DHCP server. If you are setting the IP using DHCP, always make sure you add/remove additional DNS Client Servers from there. In my situation, there was no DHCP server, hence the detailed blog post.

Prerequsites

We are going to implement this configuration via Microsoft Intune using the Scripts:

• The necessary Microsoft Intune permissions to create, the PowerShell Scripts.
• A device group available within Microsoft Entra with all the devices you want to target this change.

PowerShell Script for DNSClient (Additional DNS Servers)

Save the below script and place on the desktop and we shall be uploading it to Microsft Intune portal – “AddDNSClient.ps1″

• Please enter the proper DNS Server Address within the script based on your environment and requirement. In the example below the existing two DNS servers are 8.8.8.8 and 8.8.8.4. We are adding additional two DNS Servers 9.9.9.9 and 9.9.9.4.

$dnsclient=Get-DnsClient  | Get-DnsClientServerAddress | where{$_.ServerAddresses -contains "8.8.8.8" -or $_.ServerAddresses -contains "8.8.8.4"}
foreach($nic in $dnsclient){
Set-DnsClientServerAddress -InterfaceIndex $nic.InterfaceIndex -ServerAddresses ("8.8.8.8","8.8.8.4","9.9.9.9","9.9.9.4")
}

Create a script policy and assign it – Intune

1. Sign in to the Microsoft Intune admin center.
2. Select Devices > Scripts > Add > Windows 10 and later.
3. In Basics, enter the following properties, and select Next:
   • Name: AddDNSClientServers
   • Description: Additional DNS Server 3 & 4
   • 
4. In Script settings, enter the following properties, and select Next:
   • Script location: Browse to the PowerShell script. saved previously and upload it (AddDNSClient.ps1)
   • Run this script using the logged on credentials: Select No.
   • Enforce script signature check: Select No 
   • Run script in 64-bit PowerShell host: Select Yes to run the script in a 64-bit PowerShell host on a 64-bit client architecture.
   • 
5. Select Assignments > Select groups to include. Add the AAD group “Win11-P-DG”
   • 

Wait for approx. 15-20 minutes and the policy will apply to the managed devices. (Machine Win11-Intune-15)

Managed Device

You can validate that the settings have been applied to the client by going to the path – C:\ProgramData\Microsoft\IntuneManagementExtension\Logs and opening the file IntuneManagementExtension.txt. I copied the policy ID – cf09649b-78b7-4d98-8bcc-b122c29e5527 from the Intune portal hyperlink and searched within the log file. We can see the policy has been applied successfully.

I hope you will find this helpful information for applying additional DNS servers via Intune – Scripts and PowerShell. Please let me know if I have missed any steps or details, and I will be happy to update the post.

Thanks,
Aresh Sarkari

Tags: MEM, Microsoft, Microsoft Entra, Microsoft Intune, MSIntune, PowerShell