Merge pull request #19 from niwelton/patch-1

Update dynamic-keywords.md
This commit is contained in:
Paolo Matarazzo 2024-02-06 09:44:10 -05:00 committed by GitHub
commit 761c68c3d1
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

View File

@ -82,7 +82,6 @@ The following are requirements for the FQDN feature:
- [Chrome][HTTP-1] - [Chrome][HTTP-1]
- [Firefox][HTTP-2] - [Firefox][HTTP-2]
- The device's default DNS resolution settings apply. This feature doesn't provide DNS security or functionality changes - The device's default DNS resolution settings apply. This feature doesn't provide DNS security or functionality changes
- For Microsoft Edge version 109 and later, configure the browser to use the default system DNS through [this policy][EDGE-2]. For more information, see [Configure Microsoft Edge policy settings on Windows devices][EDGE-3]
> [!TIP] > [!TIP]
> You can also download the ADMX file from there, follow the directions, and configure it via gpedit.msc for local testing. > You can also download the ADMX file from there, follow the directions, and configure it via gpedit.msc for local testing.
@ -136,7 +135,7 @@ Get-NetFirewallDynamicKeywordAddress -AllAutoResolve
### Hydrate FQDN rules ### Hydrate FQDN rules
The following sample scripts read the current Windows Firewall configuration, extract FQDN-based rules, and perform DNS resolution on each domain. The result is that the IP addresses for those rules get populated. The following sample scripts read the current Windows Firewall configuration, extract FQDN-based rules, and perform DNS resolution on each domain. The result is that the IP addresses for those rules get "prehydrated."
```PowerShell ```PowerShell
Get-NetFirewallDynamicKeywordAddress -AllAutoResolve |` Get-NetFirewallDynamicKeywordAddress -AllAutoResolve |`