The BIND 9.x server implementation must be configured with a channel to send audit records to a local file.

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
low	V-207547	SRG-APP-000125-DNS-000012	BIND-9X-001041	SV-207547r879582_rule	2024-02-15	2

Description
DNS software administrators require DNS transaction logs for a wide variety of reasons including troubleshooting, intrusion detection, and forensics. Ensuring that the DNS transaction logs are recorded on the local system will provide the capability needed to support these actions.

ℹ️ Check
Verify that the BIND 9.x server is configured to send audit logs to a local log file. NOTE: syslog and local file channel must be defined for every defined category. Inspect the "named.conf" file for the following: logging { channel local_file_channel { file "path_name" versions 3; print-time yes; print-severity yes; print-category yes; }; category category_name { local_file_channel; }; If a logging channel is not defined for a local file, this is a finding. If a category is not defined to send messages to the local file channel, this is a finding.

ℹ️ Check

Verify that the BIND 9.x server is configured to send audit logs to a local log file. NOTE: syslog and local file channel must be defined for every defined category. Inspect the "named.conf" file for the following: logging { channel local_file_channel { file "path_name" versions 3; print-time yes; print-severity yes; print-category yes; }; category category_name { local_file_channel; }; If a logging channel is not defined for a local file, this is a finding. If a category is not defined to send messages to the local file channel, this is a finding.

✔️ Fix
Edit the "named.conf" file and add the following: logging { channel local_file_channel { file "path_name" versions 3; print-time yes; print-severity yes; print-category yes; }; category category_name { local_file_channel; }; }; Restart the BIND 9.x process.