OpenControls Logo

STIG Viewer

STIGViewer Support

All authoritative DNS service members for a zone must be geographically dispersed.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-233859IDNS-8X-400001SV-233859r1156964_ruleCCI-000366medium
Description
In addition to network-based dispersion, authoritative name servers must be also be dispersed geographically. In other words, in addition to being located on different network segments, the authoritative name servers must not all be located within the same building. One approach that some organizations follow is to locate some authoritative name servers in their own premises and others in their ISP's data centers or in partnering organizations. A network administrator may choose to use a "hidden" master authoritative server and have only secondary servers visible on the network. A hidden master authoritative server is an authoritative DNS server in which the IP address does not appear in the name server set for a zone. If the master authoritative name server is "hidden", a secondary authoritative name server may reside in the same building as the hidden master.
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-233859r1156964_chk)

1. Navigate to Data Management >> DNS >> Zones tab. 2. Review each zone by clicking "Edit" and inspecting the "DNS service members" tab. 3. Review the DNS service member records for each zone hosted and confirm that each authoritative DNS service member is located at a different physical location than the remaining DNS service members. 4. Infoblox supports designation as a "stealth" DNS service member, which will not have an NS record. If all DNS service members for which NS records are published within a zone are not physically at different locations, this is a finding.

Fix Text (F-37009r1082605_fix)

Configure the authoritative DNS service members to be geographically dispersed. Most optimal to least optimal (to provide context): - DNS service members are located on different continents. - DNS service members are located on the same continent, with greatest possible geographic dispersity. - DNS service members are located in different states/provinces. - DNS service members are located in different cities. - DNS service members are located in different buildings. - DNS service members are located in different data centers. - DNS service members are located at opposite ends of the same data center. - If moving DNS service members is not feasible, reconfigure one of the co-located service members to be a hidden primary.