OpenControls Logo

STIG Viewer

STIGViewer Support

Primary authoritative DNS service members must be configured to only receive zone transfer requests from specified secondary DNS service members.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-233871IDNS-8X-400013SV-233871r1082637_ruleCCI-000366medium
Description
Authoritative name servers (especially primary name servers) must be configured with an allow-transfer access control sub-statement designating the list of hosts from which zone transfer requests can be accepted. These restrictions address the denial-of-service threat and potential exploits from unrestricted dissemination of information about internal resources. Based on the need-to-know, only the secondary name servers need to refresh their zone files periodically. Zone transfer from primary name servers must be restricted to secondary name servers. The zone transfer must be completely disabled in the secondary name servers. The address match list argument for the allow-transfer sub-statement must consist of IP addresses of secondary name servers and stealth secondary name servers.
STIGDate
Infoblox 8.x DNS Security Technical Implementation Guide2026-06-03

Related Frameworks

1 mapping across 5 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (8) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

CFG-01Configuration Management Program
1.00
END-01Endpoint Device Management (EDM)
1.00
END-04Malicious Code Protection (Anti-Malware)
1.00
END-06Endpoint File Integrity Monitoring (FIM)
1.00
MON-01Continuous Monitoring
1.00
MON-01.7File Integrity Monitoring (FIM)
1.00
CFG-02Secure Baseline Configurations
0.50
CFG-02.7Approved Configuration Deviations
0.50
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (100) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AC-12Session Termination
1.00
AC-16(1)Dynamic Attribute Association
1.00
AC-17(1)Monitoring and Control
1.00
AC-2Account Management
1.00
AC-2(1)Automated System Account Management
1.00
AC-2(11)Usage Conditions
1.00
AC-2(3)Disable Accounts
1.00
AC-2(4)Automated Audit Actions
1.00
AC-24(1)Transmit Access Authorization Information
1.00
AC-25Reference Monitor
1.00

+90 more (top 10 by confidence shown)

NIST 800-1710 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (2) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

3.4.1
1.00
3.4.2
1.00
CCI1 mapping
CCI-000366
1.00
NIST CSF 2.00 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (5) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

DE.CM-09
1.00
PR.PS-01
1.00
PR.DS-10
0.50
PR.PSPlatform Security
0.50
PR.PS-05
0.50

Who does this work

10 NICE work roles and 9 EC-Council certifications.

This is an inference across published mappings, not a single claim by anyone. This check maps to a control, which maps to a Cybersecurity Framework outcome, which NIST assigns to the work roles below. EC-Council separately maps its certifications to those same roles.

A certification prepares someone for a role. It is not evidence that a holder is qualified, and neither NIST nor EC-Council has stated that any certification here addresses this check.

Work-role assignments published by NIST (NICE Framework Components 2.2.0 and the CSF 2.0 OLIR crosswalk). Certification mappings published by EC-Council.

Details

Check Text (C-233871r1082637_chk)

Infoblox Grid members do not use DNS zone transfers to exchange DNS data within a single Grid. Communication between Grid members is via a distributed database over a secure Virtual Private Network (VPN). 1. Navigate to the Data Management >> DNS >> Zones tab. 2. Review each zone by clicking "Edit" and inspecting the "DNS service members" tab. 3. Note all external DNS service members, those NOT identified as Type "Grid" (Primary or Secondary). 4. Click the "Zone Transfers" tab. 5. Verify that only the external non-Grid DNS service members identified as DNS service members for the zone or authorized stealth servers are the only systems authorized to perform zone transfers as authorized by a "Named ACL" or "Set of ACEs". 6. When complete, click "Cancel" to exit the "Properties" screen. If Access Controls Lists (ACLs) are not configured for zone transfers to external non-Grid servers, this is a finding.

Fix Text (F-37021r611134_fix)

1. Navigate to the Data Management >> DNS >> Zones tab. 2. Select the zone and click "Edit". Select the "Zone Transfers" tab and configure access control (ACL or Access Control Entries [ACE]) on each grid member that communicates with an external secondary. 3. When complete, click "Save & Close" to save the changes and exit the "Properties" screen. 4. Perform a service restart if necessary.