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

The BIND 9.x server implementation must implement internal/external role separation.

DISA Rule

SV-272399r1124058_rule

Vulnerability Number

V-272399

Group Title

SRG-APP-000516-DNS-000101

Rule Version

BIND-9X-001430

Severity

CAT II

CCI(s)

• CCI-000366 - Implement the security configuration settings.

Weight

10

Fix Recommendation

Edit the "named.conf" file.

Configure the internal and external view statements to use separate network segments.

Configure all internal view statements to be listed before any external view statement.

Restart the BIND 9.x process.

Check Contents

Severity override guidance:

If the internal and external views are on separate network segments, this finding may be downgraded to a CAT II.

If the BIND 9.x name server is not configured for split DNS, this is not applicable.

Verify that the BIND 9.x server is configured to use separate views and address space for internal and external DNS operations when operating in a split configuration.

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

view "internal" {
match-clients { <ip_address> | <address_match_list> };
zone "example.com" {
type Primary;
file "internals.example.com";
};
};
view "external" {
match-clients { <ip_address> | <address_match_list> };
zone "example.com" {
type Primary;
file "externals.db.example.com";
allow-transfer { Secondarys; };
};
};

If an external view is listed before an internal view, this is a finding.

If the internal and external views are on the same network segment, this is a finding.

Note: BIND 9.x reads the "named.conf" file from top to bottom. If a less stringent "match-clients" statement is processed before a more stringent "match-clients" statement, the more stringent statement will be ignored. With this in mind, all internal view statements must be listed before any external view statement in the "named.conf" file.

Vulnerability Number

V-272399

Documentable

False

Rule Version

BIND-9X-001430

Severity Override Guidance

Severity override guidance:

If the internal and external views are on separate network segments, this finding may be downgraded to a CAT II.

If the BIND 9.x name server is not configured for split DNS, this is not applicable.

Verify that the BIND 9.x server is configured to use separate views and address space for internal and external DNS operations when operating in a split configuration.

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

view "internal" {
match-clients { <ip_address> | <address_match_list> };
zone "example.com" {
type Primary;
file "internals.example.com";
};
};
view "external" {
match-clients { <ip_address> | <address_match_list> };
zone "example.com" {
type Primary;
file "externals.db.example.com";
allow-transfer { Secondarys; };
};
};

If an external view is listed before an internal view, this is a finding.

If the internal and external views are on the same network segment, this is a finding.

Note: BIND 9.x reads the "named.conf" file from top to bottom. If a less stringent "match-clients" statement is processed before a more stringent "match-clients" statement, the more stringent statement will be ignored. With this in mind, all internal view statements must be listed before any external view statement in the "named.conf" file.

Check Content Reference

M

Target Key

5687