Skip to content

Commit d7d4d1b

Browse files
authored
Update troubleshoot-zero-trust-dns-guidance.md
Edit review per CI 8098
1 parent 66a57d2 commit d7d4d1b

1 file changed

Lines changed: 12 additions & 12 deletions

File tree

support/windows-client/windows-security/troubleshoot-zero-trust-dns-guidance.md

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -15,15 +15,15 @@ appliesto:
1515
---
1616
# Zero Trust DNS troubleshooting guidance
1717

18+
This article shows you how to diagnose common connectivity and configuration issues that affect Zero Trust Domain Name System (ZTDNS) services, and how to use ZTDNS logs. The troubleshooting steps in this article help you maintain network security while making sure that legitimate applications and services continue to work correctly.
19+
1820
After you deploy Zero Trust Domain Name System (ZTDNS) services, use this guidance if you experience any of the following symptoms:
1921

2022
- Application connectivity failures
2123
- DNS resolution errors or timeouts
2224
- Unexpected network blocks or service disruptions
2325
- Network access and ZTDNS configuration issues
2426

25-
This article shows you how to diagnose common connectivity and configuration issues, and how to use ZTDNS logs. The troubleshooting steps in this article help you maintain network security while ensuring that legitimate applications and services continue to work properly.
26-
2727
## Best practices to avoid ZTDNS issues
2828

2929
- **Before you deploy and enforce ZTDNS organization-wide**
@@ -33,11 +33,11 @@ This article shows you how to diagnose common connectivity and configuration iss
3333
- **Maintaining the ZTDNS deployment**
3434
- When you add IP exceptions, document what exception was made and why.
3535
- To understand traffic patterns and identify issues early, monitor the Event Viewer logs.
36-
- To to optimize ZTDNS deployment, conduct periodical reviews of the cofiguration and logs.
36+
- To optimize ZTDNS deployment, conduct periodical reviews of the cofiguration and logs.
3737

3838
## Troubleshooting checklist
3939

40-
If you experience connectivity issues after you deploy and enforce ZTDNS, follow these steps:
40+
If you experience connectivity issues after you deploy and enforce ZTDNS, follow these steps.
4141

4242
### Step 1: Verify that the trusted DNS servers are configured correctly
4343

@@ -47,7 +47,7 @@ Make sure that at least one trusted DNS server uses ZTDNS. Open a Windows Comman
4747
netsh ztdns show server
4848
```
4949

50-
This command displays all the trusted DNS servers that use Zero Trust DNS (ZTDNS), including their protocol (DoH or DoT), IP address, and priority settings.
50+
This command displays all the trusted DNS servers that use Zero Trust DNS, including their protocol (DoH or DoT), IP address, and priority settings.
5151

5252
### Step 2: Test the connectivity to the trusted DNS servers
5353

@@ -65,11 +65,11 @@ Resolve-DnsName -Name <domain-name> -Server <dns-server-ip>
6565

6666
If these commands don't succeed, see [DNS troubleshooting guidance](../../windows-server/networking/troubleshoot-dns-guidance.md).
6767

68-
When these commands resolve successfully, check end-to-end connectivity by pinging the resolved IP address.
68+
After these commands resolve successfully, check the end-to-end connectivity by pinging the resolved IP address.
6969

7070
### Step 3: Test domain name resolution
7171

72-
To use the Windows DNS client to test DNS resolution, on a client computer, run the following command at a Windows command prompt:
72+
To use the Windows DNS client to test DNS resolution, go to a client computer, and run the following command at a Windows command prompt:
7373

7474
```console
7575
ping <allowed-domain-name>
@@ -108,9 +108,9 @@ netsh ztdns show trustedca
108108

109109
Resolve any issues that you find.
110110

111-
### Step 5 (Advanced) Test connectivity in audit mode
111+
### Step 5 (Advanced): Test connectivity in audit mode
112112

113-
If you suspect configuration issues, temporarily enable audit mode and then test connectivity when ZTDNS isn't enforced. In audit mode, Windows logs instances where ZTDNS would block connections if it were fully enforced. To enable audit mode for ZTDNS, run the following command:
113+
If you suspect configuration issues, temporarily enable audit mode, and then test connectivity when ZTDNS isn't enforced. In audit mode, Windows logs instances in which ZTDNS is expected to block connections if it's fully enforced. To enable audit mode for ZTDNS, run the following command:
114114

115115
```console
116116
netsh ztdns set state enable=yes audit=yes
@@ -139,9 +139,9 @@ After you enforce ZTDNS, users experience the following symptoms:
139139
To troubleshoot these issues, follow these steps:
140140

141141
1. Check the BlockedConnections log for recent blocked attempts. For more information about this log, see [How to find ZTDNS logs](#how-to-find-ztdns-logs).
142-
1. Identify the blocked IP addresses that the application and the destination use.
142+
1. Identify the blocked IP addresses that the application and destination use.
143143
1. Check whether the application requires IP exceptions (for example, WebRTC applications require exceptions).
144-
1. To add an exception (if needed), run `netsh ztdns add exception`.
144+
1. To add an exception (if it's necessary), run `netsh ztdns add exception`.
145145

146146
### DNS resolution failures
147147

@@ -170,4 +170,4 @@ The ZTDNS folder lists three log categories. The following table describes the t
170170
| - | - | - | - |
171171
| BlockedConnections | Contains entries that document the connections that ZTDNS blocks. | <ul><li>Time of the blocked connection</li><li>Source IP address and port</li><li>Destination IP address and port</li><li>Name of the initiating process</li></ul> | Review this log to identify applications or services that might need exceptions. |
172172
| Operational | Contains entries that document changes in the ZTDNS configuration and service state. | <ul><li>ZTDNS service status changes</li><li>Configuration changes</li><li>System events that relate to ZTDNS operations</li></ul> | Review this log to monitor the health and configuration of ZTDNS. |
173-
| PermittedConnections | Contains entries that document any connections that ZTDNS allows. | <ul><li>Time of the allowed connection</li><li>Source IP address and port</li><li>Destination IP address and port</li><li>Name of the initiating process</li></ul> | Review this log to verify that ZTDNS allows the expected connections.<br/><br/>**Note:** By default, this category is disabled. To use it, in the left panel, right-click **PermittedConnections**, and then select **Enable Log**. |
173+
| PermittedConnections | Contains entries that document any connections that ZTDNS allows. | <ul><li>Time of the allowed connection</li><li>Source IP address and port</li><li>Destination IP address and port</li><li>Name of the initiating process</li></ul> | Review this log to verify that ZTDNS allows the expected connections.<br/><br/>**Note:** By default, this category is disabled. To use it, go to the left panel, right-click **PermittedConnections**, and then select **Enable Log**. |

0 commit comments

Comments
 (0)