Information
Use the include option to add the generated key into named.conf.
Rationale:
Although the key configuration may be done directly in the named.conf file, putting it in a separate file will limit the number of times it needs to be viewed. It is essential that this secret be protected properly by having limited file permissions (same as the named.conf), and to be protected in transit to the other DNS server.
NOTE: Nessus has provided the target output to assist in reviewing the benchmark to ensure target compliance.
Solution
1. Ensure that the file is placed in the appropriate chroot-ed directory on each system.
2. Use the include option to have BIND import the key when started on each server.
3. Verify that the files permissions are limited.