STIGQter: STIG Summary: Microsoft Windows 2012 Server Domain Name System Security Technical Implementation Guide Version: 2 Release: 2 Benchmark Date: 23 Apr 2021: STIGQter: STIG Summary: Microsoft Windows 2012 Server Domain Name System Security Technical Implementation Guide Version: 2 Release: 2 Benchmark Date: 23 Apr 2021:SV-215590r561297_rule
V-215590
SRG-APP-000516-DNS-000101
WDNS-CM-000021
CAT II
10
Configure separate DNS servers for each of the external and internal networks.
Log on to the DNS server using the Domain Admin or Enterprise Admin account or Local Administrator account.
Press Windows Key + R, execute dnsmgmt.msc.
On the opened DNS Manager snap-in from the left pane, expand the server name for the DNS server, and then expand Forward Lookup Zones.
From the expanded list, review each zone.
Consult with the DNS Admin to determine if any of the zones also have hostnames needing to be resolved from the external network.
If the zone is split between internal and external networks, verify separate DNS servers have been implemented for each network.
If internal and external DNS servers have not been implemented for zones which require resolution from both the internal and external networks, this is a finding.
V-215590
False
WDNS-CM-000021
Log on to the DNS server using the Domain Admin or Enterprise Admin account or Local Administrator account.
Press Windows Key + R, execute dnsmgmt.msc.
On the opened DNS Manager snap-in from the left pane, expand the server name for the DNS server, and then expand Forward Lookup Zones.
From the expanded list, review each zone.
Consult with the DNS Admin to determine if any of the zones also have hostnames needing to be resolved from the external network.
If the zone is split between internal and external networks, verify separate DNS servers have been implemented for each network.
If internal and external DNS servers have not been implemented for zones which require resolution from both the internal and external networks, this is a finding.
M
4016