When you configure Microsoft Windows DNS Server to send logs through NXLog to USM Anywhere, you can use the Windows DNS Server plugin to translate the raw log data into normalized events for analysis.
Integrating Microsoft DNS Server and NXLog
Before you configure Microsoft Windows DNS Server to send logs to USM Anywhere through NXLog, you need to enable debug logging on the DNS server.
Configure DNS Server Debug Logging
To enable DNS server debug logging
- From the Windows Start Menu, select All Programs > Administrative Tools > DNS.
- From the console tree, right-click the applicable DNS server, and then click Properties.
Click the Debug Logging tab.
Select Log packets for debugging.
The most useful debug logging output comes from selecting at least three options:
- One option under Packet direction
- One option under Transport protocol
- At least one more option in another category
- (Optional) In addition to selecting events for the DNS debug log file, you can specify the file name, location, and a maximum file size for the file. However, in most cases, the default selections are adequate.
(Optional) Consider limiting the traffic captured by applying filters:
- Select Filter packets by IP address.
- Add the appropriate IP addresses by clicking Filter.
Warning: Do not select the Details option, because it produces logs in multi-line format instead of single-line, which the USM Anywhere plugins cannot process.
Before you configure the integration, you must have the IP Address of the USM AnywhereUSM Appliance Sensor.
To configure NXLog to send log data to USM Anywhere
The Windows DNS Server plugin will automatically process all messages when the raw message contains "SourceName":"DNS".
Available Plugin Fields
The following plugin fields are important attributes extracted from the syslog message. USM Anywhere reports use these fields, and you can also reference them when creating custom reports. In addition to reporting, the USM Anywhere correlation rules make use of these fields.
customfield_0 - Header
customfield_1 - Return Code
customfield_2 - Return Code Description
customfield_3 - Resource Type ID
customfield_4 - Resource Type Description
For troubleshooting, refer to the vendor documentation: