The Infoblox DNS service member must use current and valid root DNS service members.

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
medium	V-233874	SRG-APP-000516-DNS-000102	IDNS-8X-400016	SV-233874r1082643_rule	2025-03-11	1

Description
All caching name servers must be authoritative for the root zone because, without this starting point, they would have no knowledge of the DNS infrastructure and thus would be unable to respond to any queries. An adversary could change the root hints and direct the caching name server to a bogus root server. At that point, every query response from that name server is suspect, which would give the adversary substantial control over the network communication of the name servers' clients. When authoritative servers are sent queries for zones for which they are not authoritative, and configured as a noncaching server (as recommended), they can either be configured to return a referral to the root servers or to refuse to answer the query. The recommendation is to configure authoritative servers to refuse to answer queries for any zones for which they are not authoritative. This is more efficient for the server and allows it to spend more of its resources serving its intended purpose: answering authoritatively for its zone.

Description

All caching name servers must be authoritative for the root zone because, without this starting point, they would have no knowledge of the DNS infrastructure and thus would be unable to respond to any queries. An adversary could change the root hints and direct the caching name server to a bogus root server. At that point, every query response from that name server is suspect, which would give the adversary substantial control over the network communication of the name servers' clients. When authoritative servers are sent queries for zones for which they are not authoritative, and configured as a noncaching server (as recommended), they can either be configured to return a referral to the root servers or to refuse to answer the query. The recommendation is to configure authoritative servers to refuse to answer queries for any zones for which they are not authoritative. This is more efficient for the server and allows it to spend more of its resources serving its intended purpose: answering authoritatively for its zone.

ℹ️ Check
Review the Root DNS service members configured and validate that the entries are correct. "G" and "H" root servers are required on the NIPRNet as a minimum. Note: Validate against the current available DNS root list at the time of check. 1. Validate the current root DNS service member list using external tools at the time of the check. 2. Navigate to Data Management >> DNS >> Grid DNS Properties. 3. Toggle Advanced mode and review the "Root DNS service members" tab to ensure it is configured correctly. If valid root DNS service members are not configured, this is a finding.

ℹ️ Check

Review the Root DNS service members configured and validate that the entries are correct. "G" and "H" root servers are required on the NIPRNet as a minimum. Note: Validate against the current available DNS root list at the time of check. 1. Validate the current root DNS service member list using external tools at the time of the check. 2. Navigate to Data Management >> DNS >> Grid DNS Properties. 3. Toggle Advanced mode and review the "Root DNS service members" tab to ensure it is configured correctly. If valid root DNS service members are not configured, this is a finding.

✔️ Fix
1. Navigate to Data Management >> DNS >> Grid DNS Properties. 2. Toggle Advanced mode and select the "Root DNS service members" tab. 3. Use the radio button to select "Use custom root DNS service members" and configure the desired root DNS service members. 4. When complete, click "Save & Close" to save the changes and exit the "Properties" screen. 5. Perform a service restart if necessary.