Skip to content
Catalogs
XCCDF
Domain Name System (DNS) Security Requirements Guide
SRG-APP-000516
The DNS implementation must ensure each NS record in a zone file points to an active name server authoritative for the domain specified in that record.
The DNS implementation must ensure each NS record in a zone file points to an active name server authoritative for the domain specified in that record. An XCCDF Rule
The DNS implementation must ensure each NS record in a zone file points to an active name server authoritative for the domain specified in that record.
Medium Severity
<VulnDiscussion>Poorly constructed NS records pose a security risk because they create conditions under which an adversary might be able to provide the missing authoritative name services that are improperly specified in the zone file. The adversary could issue bogus responses to queries that clients would accept because they learned of the adversary's name server from a valid authoritative name server, one that need not be compromised for this attack to be successful. The list of slave servers must remain current within 72 hours of any changes to the zone architecture that would affect the list of slaves. If a slave server has been retired or is not operational but remains on the list, then an adversary might have a greater opportunity to impersonate that slave without detection, rather than if the slave were actually online. For example, the adversary may be able to spoof the retired slave's IP address without an IP address conflict, which would not be likely to occur if the true slave were active.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>