大网数据广告活动
网络与域名解析

Troubleshooting Domain Name System (DNS) issues

· 52CE 我爱测

This article introduces how to collect data when DNS issues occur.

[!div class="nextstepaction"] <a href="https://vsa.services.microsoft.com/v1.0/?partnerId=7d74cf73-5217-4008-833f-87a1a278f2cb&flowId=DMC&initialQuery=31806264" target='_blank'>Try our Virtual Agent</a> - It can help you quickly identify and fix common DNS issues.

Domain Name resolution issues can be broken down into client-side and server-side issues. In general, you should start with client-side troubleshooting unless you determine during the scoping phase that the issue is definitely occurring on the server side.

Data Collection

We recommend that you simultaneously collect data on both the client and server sides when the issue occurs. However, depending on the actual issue, you can start your collection at a single data set on either the DNS client or DNS server.

To collect a Windows Networking Diagnostic from an affected client and its configured DNS server, follow these steps:

  1. Start network captures on the client and server:

    netsh trace start capture=yes tracefile=c:\%computername%_nettrace.etl
    
  2. Clear the DNS cache on the DNS client by running the following command:

    ipconfig /flushdns
    
  3. Reproduce the issue.

  4. Stop and save traces:

    netsh trace stop
    
  5. Save the Nettrace.cab files from each computer. This information will be helpful when you contact Microsoft Support.

Source: Microsoft Learn / Windows Server documentation by Microsoft and contributors (upstream author metadata: robinharwood). Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / Windows Server documentation
适用范围
Windows Server · Source date 8/8/2019
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。