deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-12 21:37:22 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Merge branch 'pm-firewall-reusable-settings' of github.com:paolomatarazzo/windows-docs-pr into pm-firewall-reusable-settings

Browse Source
This commit is contained in:
Paolo Matarazzo 2024-02-14 08:57:08 +01:00
commit 4745602db3
1 changed files with 1 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
windows/security/operating-system-security/network-security/windows-firewall/dynamic-keywords.md
View File

@ -75,7 +75,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.
@ -129,7 +128,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 |`