Open in the explorer

Configure multicast DNS (mDNS) protocol

Configurer le protocole DNS de multidiffusion (mDNS)

Type
Computer
GPO path
Computer Configuration › Policies › Administrative Templates › Network › DNS Client FR: Configuration ordinateur › Stratégies › Modèles d'administration › Réseau › Client DNS
Supported on
At least Windows Server 2016, Windows 10 Version 1703 FR: Windows Server 2016, Windows 10 version 1703 ou versions supérieures
ADMX file
DnsClient.admx
Internal name
DnsClient/DNS_MDNS

Explanation

Specifies if the DNS client will perform name resolution over mDNS.

If you enable this policy, the DNS client will use mDNS protocol.

If you disable this policy setting, or if you do not configure this policy setting, the DNS client will use locally configured settings.

French text from Windows 11 26H2

Spécifie si le client DNS effectue la résolution de noms sur mDNS.

Si vous activez cette stratégie, le client DNS utilise le protocole mDNS.

Si vous désactivez ce paramètre de stratégie ou si vous ne le configurez pas, le client DNS utilise les paramètres configurés localement.

Use cases

Indicates whether the DNS client resolves names over mDNS (multicast DNS). When enabled, the policy forces the protocol on; when disabled or not configured, the client applies its local settings (registry value EnableMDNS set to 1 or 0).

Microsoft presents mDNS as the modern standard for multicast name discovery and uses it as the first step toward turning NetBIOS and LLMNR off by default. So tune it together with the NetBIOS policy and the multicast name resolution policy: decide explicitly which local name protocols remain allowed across the estate.

Microsoft source: Aligning on mDNS: ramping down NetBIOS name resolution and LLMNR

Registry

HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows NT\DNSClient
Value name
EnableMDNS
StateValue written
EnabledREG_DWORD = 1
DisabledREG_DWORD = 0

PowerShell

PowerShell commands that write to the registry what the policy would write. Values in angle brackets (<…>) must be replaced.

Writing directly to the registry bypasses Group Policy: if a GPO manages this value, it will be rewritten at the next gpupdate; otherwise the value stays in place (the "tattooing" effect). Prefer a GPO or, locally, LGPO.exe. Run PowerShell as administrator for HKLM. Some policies need a restart or gpupdate /force.

Enable

# Enable: DnsClient/DNS_MDNS
$k = 'HKLM:\Software\Policies\Microsoft\Windows NT\DNSClient'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
Set-ItemProperty -Path $k -Name 'EnableMDNS' -Value 1 -Type DWord

Disable

# Disable: DnsClient/DNS_MDNS
$k = 'HKLM:\Software\Policies\Microsoft\Windows NT\DNSClient'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
Set-ItemProperty -Path $k -Name 'EnableMDNS' -Value 0 -Type DWord

Revert to "Not configured"

# Revert to "Not configured": DnsClient/DNS_MDNS
$k = 'HKLM:\Software\Policies\Microsoft\Windows NT\DNSClient'
Remove-ItemProperty -Path $k -Name 'EnableMDNS' -ErrorAction SilentlyContinue

Availability

Windows 11

✓ 26H2✓ 25H2✓ 24H2— 23H2— 22H2— 21H2

Windows 10

— 22H2— 21H2— 21H1— 20H2— 2004— 1909— 1903— 1809— 1803— 1709— 1703— 1607— 1511— 1507

Windows Server

✓ 2025— 2022— 2016