STIGhubSTIGhub
STIGsSearchCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 5 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Domain Name System (DNS) Security Requirements Guide

V-205248

CAT II (Medium)

The platform on which the name server software is hosted must be configured to send outgoing DNS messages from a random port.

Rule ID

SV-205248r961863_rule

STIG

Domain Name System (DNS) Security Requirements Guide

Version

V4R2

CCIs

CCI-000366

Discussion

OS configuration practices as issued by the US Computer Emergency Response Team (US CERT) and the National Institute of Standards and Technology's (NIST's) National Vulnerability Database (NVD), based on identified vulnerabilities that pertain to the application profile into which the name server software fits, should be always followed. In particular, hosts that run the name server software should not provide any other services and therefore should be configured to respond to DNS traffic only. In other words, the only allowed incoming ports/protocols to these hosts should be 53/udp and 53/tcp. Outgoing DNS messages should be sent from a random port to minimize the risk of an attacker guessing the outgoing message port and sending forged replies.

Check Content

Review the DNS configuration. Determine if a static port is being used to send outgoing DNS messages or whether it is configured to use a random port.

If the DNS configuration specifies a static port to be used for outgoing DNS messages rather than a random port, this is a finding.

Fix Text

Configure the DNS server to use a random port for outgoing DNS messages.