Details

DNS software administrators require DNS transaction logs for a wide variety of reasons including troubleshooting, intrusion detection, and forensics. Ensuring that the DNS transaction logs are recorded on the local system will provide the capability needed to support these actions. Sending DNS transaction data to the null channel would cause a loss of important data.

Solution

Edit the ‘named.conf’ file.

Remove any instance of the following:

category null { null; };

Restart the BIND 9.x process.

Supportive Information

The following resource is also helpful.

• https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_BIND_9-x_V2R2_STIG.zip

This security hardening control applies to the following category of controls within NIST 800-53: Audit and Accountability.This control applies to the following type of system Unix.

References

• 800-53|AU-9(2)
• CAT|III
• CCI|CCI-001348
• Rule-ID|SV-207540r612253_rule
• STIG-ID|BIND-9X-001017
• STIG-Legacy|SV-87003
• STIG-Legacy|V-72379
• Vuln-ID|V-207540

Source

• Tenable.com/audits