The Windows DNS Server's IP address must be statically defined and configured locally on the server.
An XCCDF Rule
Description
<VulnDiscussion>The major threat associated with DNS forged responses or failures is the integrity of the DNS data returned in the response. The principle of DNSSEC is to mitigate this threat by providing data origin authentication, establishing trust in the source. By requiring remote clients to obtain origin authentication and integrity verification assurances for the host/service name to network address resolution information obtained through the service, data origin is validated. Ensuring all name servers have static IP addresses makes it possible to configure restricted DNS communication, such as with DNSSEC, between the name servers.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>
- ID
- SV-259374r945286_rule
- Severity
- Medium
- References
- Updated
Remediation - Manual Procedure
Log on to the DNS server using the Domain Admin or Enterprise Admin account or Local Administrator account.
Locate the "Network Internet Access" icon, right-click on it, and select "Open Network & Sharing Center".
Click "Change adapter settings".