Details
NSEC records list the resource record types for the name, as well as the name of the next resource record. With this information it is revealed that the resource record type for the name queried, or the resource record name requested, does not exist. NSEC uses the actual resource record names, whereas NSEC3 uses a one-way hash of the name. In this way, walking zone data from one record to the next is prevented, at the expense of some CPU cycles both on the authoritative server as well as the resolver. To prevent giving access to an entire zone file, NSEC3 should be configured and in order to use NSEC3, RSA/SHA-1 should be used as the algorithm, as some resolvers that understand RSA/SHA-1 might not understand NSEC3. Using RSA/SHA-256 is a safe alternative.
Solution
Log on to the DNS server using the Domain Admin or Enterprise Admin account or Local Administrator account.
If not automatically started, initialize the Server Manager window by clicking its icon from the bottom left corner of the screen.
Once the Server Manager window is initialized, from the left pane, click to select the DNS category.
From the right pane, under the SERVERS section, right-click the DNS server.
From the context menu that appears, click DNS Manager.
On the opened DNS Manager snap-in from the left pane, expand the server name and then expand Forward Lookup Zones.
From the expanded list, click to select the zone.
Right-click the zone, select DNSSEC, Sign the Zone.
Re-sign the zone, using an NSEC3 algorithm (RSA/SHA-1 (NSEC3), RSA/SHA-256, RSA/SHA-512).
Supportive Information
The following resource is also helpful.
This security hardening control applies to the following category of controls within NIST 800-53: Configuration Management.This control applies to the following type of system Windows.
References
- 800-53|CM-6b.
- CAT|II
- CCI|CCI-000366
- Rule-ID|SV-215579r561297_rule
- STIG-ID|WDNS-CM-000009
- STIG-Legacy|SV-73021
- STIG-Legacy|V-58591
- Vuln-ID|V-215579