The DNS implementation must limit the number of concurrent sessions client connections to the number of allowed dynamic update clients.

Limiting the number of concurrent sessions reduces the risk of Denial of Service (DoS) to the DNS implementation. Name servers do not have direct user connections but accept client connections for queries. Original restriction on client connections should be high enough to prevent a self-imposed denial of service, after which the connections are monitored and fine-tuned to best meet the organization's specific requirements.Primary name servers also make outbound connections to secondary name servers to provide zone transfers and accept inbound connection requests from clients wishing to provide a dynamic update. Primary name servers should explicitly limit zone transfers to only be made to designated secondary name servers. Because zone transfers involve the transfer of entire zones and use TCP connections, they place substantial demands on network resources relative to normal DNS queries. Errant or malicious frequent zone transfer requests on the name servers of the enterprise can overload the master zone server and result in DoS to legitimate users. Primary name servers should be configured to limit the hosts from which they will accept dynamic updates.Additionally the number of concurrent clients, especially TCP clients, needs to be kept to a level that does not risk placing the system in a DoS state.

Check content

Review the DNS server configuration and ensure a limit has been defined for the number of inbound dynamic update sessions by defining the finite group of hosts allowed to provide those dynamic updates. If the DNS server configuration does not explicitly specify which hosts from which it accepts dynamic updates, this is a finding.

Fix text

Configure the DNS primary server to explicitly specify which hosts from which it accepts dynamic updates.

Pro Tips

Lavender hyperlinks in small type off to the right (of CSS class id, if you view the page source) point to globally unique URIs for each document and item. Copy the link location and paste anywhere you need to talk unambiguously about these things.

You can obtain data about documents and items in other formats. Simply provide an HTTP header Accept: text/turtle or Accept: application/rdf+xml.

SV-69023r1_rule The DNS implementation must limit the number of concurrent sessions client connections to the number of allowed dynamic update clients.

Vulnerability discussion

Check content

Fix text

Pro Tips