- play_arrow What's New in WinCollect
- play_arrow WinCollect Overview
- play_arrow Installation Prerequisites for WinCollect
- play_arrow WinCollect installations
- WinCollect installations
- Installing and Upgrading the WinCollect Application on JSA Appliances
- Creating an Authentication Token for WinCollect Agents
- Adding Multiple Destinations to WinCollect Agents
- Migrating WinCollect Agents After a JSA Hardware Upgrade
- Stand-alone WinCollect Installations
- WinCollect Configuration Console Overview
- Installing the Configuration Console
- Silently Installing, Upgrading, and Uninstalling WinCollect Software
- Setting an XPath Parameter During Automated Installation
- Migrating from Adaptive Log Exporter to WinCollect
- Installing the WinCollect Agent on a Windows Host
- Installing a WinCollect Agent from the Command Prompt
- Uninstalling a WinCollect Agent from the Command Prompt
- Uninstalling a WinCollect Agent from the Control Panel
- play_arrow Configuring WinCollect Agents After Installation
- Configuring WinCollect Agents After Installation
- Manually Adding a WinCollect Agent
- Deleting a WinCollect Agent
- WinCollect Destinations
- Adding Custom Entries to WinCollect Status Messages
- Forwarding Events Identifier
- Configuring Stand-alone WinCollect Agents with the Configuration Console
- Creating a WinCollect Credential
- Adding a Destination to the WinCollect Configuration Console
- Configuring a Destination with TLS in the WinCollect Configuration Console
- Adding a Device to the WinCollect Configuration Console
- Sending Encrypted Events to JSA
- Increasing UDP Payload Size
- Include Milliseconds in Event Log Timestamp
- Collecting Local Windows Logs
- Collecting Remote Windows Logs
- Changing configuration with Templates in a Stand-alone Deployment
- Configuration Options for Systems with Restricted Policies for Domain Controller Credentials
- play_arrow Troubleshooting WinCollect Deployment Issues
- Troubleshooting WinCollect Deployment Issues
- Common Problems
- Replacing the Default Certificate in JSA Generates Invalid PEM Errors
- The Statistics Subsystem
- Event ID 1003 Splits the Message in JSA
- WinCollect Files are Not Restored During a Configuration Restore
- Windows 10 (1803) Cannot Read the Security Bookmark File
- Resolving Log Source Error After WinCollect Update
- WinCollect Log File
DNS Debug Log Source Configuration Options
Use the reference information to configure the WinCollect plug-in for MicrosoftWindows DNS debug logging.
DNS debug logging can affect system performance and disk space because it provides detailed data about information that the DNS server sends and receives. Enable DNS debug logging only when you require this information.
DNS debug logging is supported on the following Windows versions:
Windows Server 2019 (including Core)
Windows Server 2016 (including Core)
Windows Server 2012 R2
Windows Server 2012
Parameter | Description |
|---|---|
File Reader Type | Reads file contents. Both options have basic Unicode encoding support for byte-order marks. If you choose the Text (file held open) option, then WinCollect maintains a shared read and write lock on the monitored log file. If you choose the Text (file open when reading) option, then WinCollect maintains a shared read and write lock on the log file only when it reads the file. |
File Monitor Type | Detects file and directory changes: The Notification-based (local) option uses the Windows file system notifications to detect changes to your DNS log. The Polling-based (remote) option monitors changes to remote files and directories. The agent polls the remote DNS log and compares the file to the last polling interval. If the log contains new entries, the entries are retrieved. |
File Pattern | The regular expression (regex) required to match the DNS debug log file set in the DNS manager. |
Root Directory | The directory where WinCollect monitors files. The directory must be Local File System for local collection, or a valid MicrosoftWindows universal naming convention (UNC) path for remote collection. This value must match the file path that is configured in your DNS manager. Note: Due to restrictions in distributed systems, the path can't be verified in the user interface. |
Include DNS Details | Includes DNS details in the Windows Server DNS debugging log. |
For more information about Microsoft DNS Debug specifications, see the Configuring DSMs Guide.
Enabling DNS Debugging on Windows Server
Enable DNS debugging on Windows Server to collect information that the DNS server sends and receives.
The DNS role must be installed on the Windows Server.
Open the DNS Manager with the following command:
dnsmgmt.msc
Right-click the DNS server and click Properties.
Click the Debug Logging tab.
Select Log packets for debugging.
In the log file, type the file path and name, and the maximum size.
Note:The file path and name, must align with the Root Directory and File Pattern that you provided when you configured the Microsoft DNS log source in JSA.
If you want to include DNS details in the log, select Details in the Other options section, and then select Include DNS Details in the log source.
Click Apply and then click OK.
