STIGQter: STIG Summary: BIND 9.x Security Technical Implementation Guide Version: 3 Release: 3 Benchmark Date: 01 Jul 2026:

The secondary name servers in a BIND 9.x implementation must be configured to initiate zone update notifications to other authoritative zone name servers.

DISA Rule

SV-272393r1124048_rule

Vulnerability Number

V-272393

Group Title

SRG-APP-000516-DNS-000088

Rule Version

BIND-9X-001370

Severity

CAT II

CCI(s)

• CCI-000366 - Implement the security configuration settings.

Weight

10

Fix Recommendation

Edit the "named.conf" file.

Configure the "notify" sub-statement in the "options" statement block to "no":

options {
notify no;
};

Configure the "notify explicit" and "also-notify" sub-statements in the zone statement block to limit zone transfer notifications to authorized secondary name servers:

zone example.com {
notify explicit;
also-notify { <ip_address>; | <address_match_list>; };

Restart the BIND 9.x process.

Check Contents

If this is a primary name server, this is not applicable.

On a secondary name server, verify that the global notify is disabled. The global entry for the name server is under the "Options" section, and notify must be disabled at this section.

Inspect the "named.conf" file for the following:

options {
notify no;
};

If the "notify" statement is missing, this is a finding.

If the "notify" statement is set to "yes", this is a finding.

Verify that zones for which the secondary server is authoritative are configured to notify other authorized secondary name servers when a zone file update has been received from the primary name server for the zone. Each zone has its own zone section.

Inspect the "named.conf" file for the following:

zone example.com {
notify explicit;
also-notify { <ip_address>; | <address_match_list>; };

If an "address match list" is used, verify that each IP address listed is an authorized secondary name server for that zone.

If the "notify explicit" statement is missing, this is a finding.

If the "also-notify" statement is missing, this is a finding.

If the "also-notify" statement is configured to notify name servers that are not authorized for that zone, this is a finding.

Vulnerability Number

V-272393

Documentable

False

Rule Version

BIND-9X-001370

Severity Override Guidance

If this is a primary name server, this is not applicable.

On a secondary name server, verify that the global notify is disabled. The global entry for the name server is under the "Options" section, and notify must be disabled at this section.

Inspect the "named.conf" file for the following:

options {
notify no;
};

If the "notify" statement is missing, this is a finding.

If the "notify" statement is set to "yes", this is a finding.

Verify that zones for which the secondary server is authoritative are configured to notify other authorized secondary name servers when a zone file update has been received from the primary name server for the zone. Each zone has its own zone section.

Inspect the "named.conf" file for the following:

zone example.com {
notify explicit;
also-notify { <ip_address>; | <address_match_list>; };

If an "address match list" is used, verify that each IP address listed is an authorized secondary name server for that zone.

If the "notify explicit" statement is missing, this is a finding.

If the "also-notify" statement is missing, this is a finding.

If the "also-notify" statement is configured to notify name servers that are not authorized for that zone, this is a finding.

Check Content Reference

M

Target Key

5687