STIGhubSTIGhub
STIGsRMF ControlsCompare
STIGhub— A free STIG search and compliance tool·STIGs updated 3 days ago
Powered by Pylon·Privacy·Terms·© 2026 Beacon Cloud Solutions, Inc.
← Back to Microsoft Windows Server Domain Name System (DNS) Security Technical Implementation Guide

V-259360

CAT II (Medium)

Nonroutable IPv6 link-local scope addresses must not be configured in any zone.

Rule ID

SV-259360r961863_rule

STIG

Microsoft Windows Server Domain Name System (DNS) Security Technical Implementation Guide

Version

V2R4

CCIs

CCI-000366

Discussion

IPv6 link-local scope addresses are not globally routable and must not be configured in any DNS zone. Like RFC1918 addresses, if a link-local scope address is inserted into a zone provided to clients, most routers will not forward this traffic beyond the local subnet.

Check Content

Log on to the DNS server using the Domain Admin or Enterprise Admin account or Local Administrator account.

Press the Windows key + R and execute "dnsmgmt.msc".

On the opened DNS Manager snap-in from the left pane, expand the server name for the DNS server and then expand "Forward Lookup Zones".

From the expanded list, click to select the zone.

Expand the "Forward Lookup Zones" folder.

Expand each zone folder and examine the host record entries. The third column titled "Data" will display the IP.

Verify this column does not contain any IP addresses that begin with the prefixes "FE8", "FE9", "FEA", or "FEB".

If any nonroutable IPv6 link-local scope addresses are in any zone, this is a finding.

Fix Text

Remove any link-local addresses and replace with appropriate Site-Local or Global scope addresses.