The host running a BIND 9.x implementation must have DNS cookies enabled.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-275938 | BIND-9X-002470 | SV-275938r1156959_rule | CCI-000366 | medium |
| Description | ||||
| DNS cookies can help prevent spoofing and cache poisoning attacks by verifying the identity of both the client and server. They do this by including a cryptographic identifier (the cookie) in DNS messages, which can be verified in future messages. This makes it difficult for an attacker to learn the cookie values and thus spoof them. | ||||
| STIG | Date | |||
| BIND 9.x Security Technical Implementation Guide | 2026-02-25 | |||
Details
Check Text (C-275938r1156959_chk)
Verify answer-cookie is enabled.
Inspect the named.conf file for the following:
options {
answer-cookie yes;
If answer-cookie is missing or set to "no", this is a finding.
Fix Text (F-79945r1123967_fix)
Edit the named.conf file:
options {
answer-cookie yes;
};
After making changes, save the named.conf file and restart the BIND service to apply the changes.