STIGhubSTIGhub
STIGhub— A free STIG search and compliance tool·STIGs updated 12 hours ago
Powered by Pylon·Privacy·Terms·Feedback·© 2026 Beacon Cloud Solutions, Inc.
← Back to Infoblox NIOS 9.x Security Technical Implementation Guide

V-285281

CAT II (Medium)

In a split DNS configuration, where separate DNS service members are used between the external and internal networks, the external DNS service member must be configured to not be reachable from inside resolvers.

Rule ID

SV-285281r1258969_rule

STIG

Infoblox NIOS 9.x Security Technical Implementation Guide

Version

V1R1

CCIs

CCI-000366

Discussion

Instead of having the same set of authoritative name servers serve different types of clients, an enterprise could have two different sets of authoritative name servers. One set, called external name servers, can be located within a DMZ; these would be the only name servers that are accessible to external clients and would serve RRs pertaining to hosts with public services (web servers that serve external web pages or provide B2C services, mail servers, etc.). The other set, called internal name servers, is to be located within the firewall and should be configured so they are not reachable from outside and hence provide naming services exclusively to internal clients.

Check Content

Verify that Infoblox is configured to restrict queries and recursion options in split DNS environments.

If a split DNS configuration is not used, this is Not Applicable. 

Validation of this configuration item requires review of the network architecture and security configuration in addition to DNS service member configuration to verify that external DNS service members are not accessible from the internal network when a split DNS configuration is implemented. 

1. Navigate to Data Management >> DNS >> Members tab. 
2. Select each grid member that is running DNS and click "Edit". Review the "Queries" tab to verify that both queries and recursion options are enabled and allowed only from the respective client networks. 

If there is no access control configured or access control does not restrict queries and recursion to the respective client network, this is a finding.

Fix Text

Navigate to Data Management >> DNS >> Members tab. 

For External DNS resolvers in a Split DNS configuration:
1. Select the Grid member(s) identified as running the External DNS service and click "Edit". 
2. Under the Queries tab, enable and configure either an Access Control List (ACL) or set of Access Control Entries (ACE) allowing external clients and denying internal clients. 
3. When complete, click "Save & Close" to save the changes and exit the "Properties" screen. 
4. Perform a service restart if necessary.

ACLs for External members should end with "Any" allow at the end after denying internal networks.