BIND-9X-001240 - On a BIND 9.x server in a split DNS configuration, where separate name servers are used between the external and internal networks, the external name server must be configured to not be reachable from inside resolvers.

Warning! Audit Deprecated

This audit has been deprecated and will be removed in a future update.

Information

Instead of having the same set of authoritative name servers serve different types of clients, an enterprise could have two different sets of authoritative name servers.

One set, called external name servers, can be located within a DMZ. These would be the only name servers that are accessible to external clients and would serve RRs pertaining to hosts with public services (web servers that serve external web pages or provide B2C services, mail servers, etc.).

The other set, called internal name servers, must be located within the firewall. They must be configured so they are not reachable from outside and therefore provide naming services exclusively to internal clients.

NOTE: Nessus has provided the target output to assist in reviewing the benchmark to ensure target compliance.

Solution

Edit the 'named.conf' file.

Configure the external view statement to server external hosts only:

view 'external' {
match-clients { <ip_address> | <address_match_list>; };
};

Restart the BIND 9.x process.

Item Details

Audit Name: DISA BIND 9.x STIG v3r1

Plugin: Unix

Control ID: 55877811693d57968e7678a8dbcb7edd136b415801e5a7a9395896565f25b149

Detections

Analytics

BIND-9X-001240 - On a BIND 9.x server in a split DNS configuration, where separate name servers are used between the external and internal networks, the external name server must be configured to not be reachable from inside resolvers.

Warning! Audit Deprecated

Information

Solution

See Also

Item Details