STIGhubSTIGhub
STIGsSearchCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 3 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to BIND 9.x Security Technical Implementation Guide

V-272430

CAT II (Medium)

The BIND 9.x server implementation must maintain at least three file versions of the local log file.

Rule ID

SV-272430r1123947_rule

STIG

BIND 9.x Security Technical Implementation Guide

Version

V3R2

CCIs

CCI-001348

Discussion

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 Content

Verify that the BIND 9.x server is configured to retain at least three versions of the local log file.

Inspect the "named.conf" file for the following:

logging {
channel local_file_channel {
file "path_name" versions 3;
size 10m;
};

If the "versions" variable is not defined, this is a finding.

If the "versions" variable is configured to retain fewer than three versions of the local log file, this is a finding.

Fix Text

Edit the "named.conf" file.

Add the "versions" variable to the end of the "file" sub-statement in the channel statement.

Configure the "versions" sub-statement to a number that is greater than or equal to "3".

Restart the BIND 9.x process.