Guest config - "Turn off multicast name resolution" expecting value 1 instead of 0
- Dominant language
- Open Policy Agent
- Stars
- 1.7k
- Forks
- 1.2k
- Avg merge
- 2d 54m
- Merged PRs (30d)
- 3
Description
I noticed that the "turn off Multicast name resolution" expects the wrong value. To turn off Multicast, you need to set the key `EnableMulticast` to 0 (in `HKLM\Software\Policies\Microsoft\Windows NT\DNSClient!EnableMulticast`).
From the Sample found here: https://github.com/Azure/azure-policy/blob/f2706e05bccaac0a7410f8613107a6ee3bd88afd/samples/GuestConfiguration/package-samples/configurations/AzureWindowsBaseline/AzureWindowsBaseline.mof#L2975
Compared to Qualys scans:
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by comparing the Guest Configuration implementation with the AzureWindowsBaseline sample linked in the issue, focusing on the HKLM\Software\Policies\Microsoft\Windows NT\DNSClient!EnableMulticast registry key. Confirm the expected value against the Qualys scan examples; done means the configuration expects 0 when multicast name resolution is turned off.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- security
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100