Release notes v1.1.0 (2026-01-23)

Added

• NEW: ContextFilter parameter for selective log parsing
  • Filter log entries by context type: PACKET (DNS queries/responses), EVENT (server events), or Note (diagnostic information)
  • Allows focused analysis on specific log entry types
  • Default: All (includes all context types)
  • Use cases: Focus on DNS traffic only, monitor server events, troubleshoot diagnostic issues
• NEW: Information field in CSV output
  • Captures detailed information for EVENT and Note context entries
  • Examples: “The DNS server has started.”, “Zone loading completed”, socket errors, internal state messages
  • Enhances visibility into DNS server operational events and diagnostics
  • Field is populated when Context is EVENT or Note; empty for PACKET entries

Changed

• BREAKING: ComputerName column now always included at the end of all output records
  • Previously: ComputerName was conditionally included at the beginning when parameter was specified
  • Now: ComputerName always present as the last column; empty when parameter not specified
  • Benefit: Consistent output structure simplifies multi-server log consolidation and automated processing
  • Impact: Existing scripts that parse column positions or expect conditional column presence must be updated

Added

• Context filtering to focus on specific log entry types (PACKET, EVENT, NOTE) via ContextFilter parameter

Improved

• Refactored comment-based help for Convert-DNSDebugLogFile for better clarity and conciseness
• Updated parameter descriptions to be more informative and actionable
• Improved example documentation with more focused and practical use cases
• Enhanced about_DNSServer.DebugLogParser help file to reflect current functionality
• Enhanced verbose logging to provide more detailed progress information during processing

• ←Previous
• Next→