The BIND 9.x server implementation must have fetches-per-server enabled.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-275937BIND-9X-002460SV-275937r1156959_ruleCCI-000366medium
Description
The fetches-per-server option in BIND 9.x configures a limit on the number of outstanding requests (fetches) allowed for a single DNS server. This rate-limiting mechanism helps protect the BIND 9.x server from being overwhelmed by excessive requests to a specific server, particularly when that server is slow or unresponsive.
STIGDate
BIND 9.x Security Technical Implementation Guide2026-02-25

Related Frameworks

4 paths across 3 frameworks
NIST 800-531 mapping
CM-6
1.00
  • DISA · V3R2 · disa_xccdf · related
  • DISA · 2025-01-23 · disa_cci_list · equivalent
NIST 800-1712 mappings
3.4.1
1.00
  • DISA · V3R2 · disa_xccdf · related
  • DISA · 2025-01-23 · disa_cci_list · equivalent
  • NIST · Rev 2 (Feb 2020, errata Jan 2021) · nist_800_171_app_d · equivalent
3.4.2
1.00
  • DISA · V3R2 · disa_xccdf · related
  • DISA · 2025-01-23 · disa_cci_list · equivalent
  • NIST · Rev 2 (Feb 2020, errata Jan 2021) · nist_800_171_app_d · equivalent
CCI1 mapping
CCI-000366
1.00
  • DISA · V3R2 · disa_xccdf · related

Details

Check Text (C-275937r1156959_chk)

Verify fetches-per-server is enabled with an organization-defined number. Inspect the named.conf file for the following: options { fetches-per-server <integer> drop ; If fetches-per-server is not enabled and set to drop, this is a finding.

Fix Text (F-79944r1123964_fix)

Modify the BIND configuration file (/etc/named.conf ). Add the fetches-per-server option to the "options" section of the configuration file. fetches-per-server <integer> drop; After making changes, reload or restart BIND to apply the new settings.