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 3 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to BIND 9.x Security Technical Implementation Guide

V-272410

CAT II (Medium)

On a BIND 9.x server, all authoritative name servers for a zone must have the same version of zone information.

Rule ID

SV-272410r1124061_rule

STIG

BIND 9.x Security Technical Implementation Guide

Version

V3R2

CCIs

CCI-000366

Discussion

It is important to maintain the integrity of a zone file. The serial number of the SOA record is used to indicate to secondary name server that a change to the zone has occurred and a zone transfer should be performed. The serial number used in the SOA record provides the DNS administrator a method to verify the integrity of the zone file based on the serial number of the last update and ensure that all secondary servers are using the correct zone file.

Check Content

Verify that the SOA record is at the same version for all authoritative servers for a specific zone.

With the assistance of the DNS administrator, identify each name server that is authoritative for each zone.

Inspect each zone file that the server is authoritative for and identify the following:

example.com. 86400 IN SOA ns1.example.com. root.example.com. (17760704;serial) 

If the SOA "serial" numbers are not identical on each authoritative name server, this is a finding.

Fix Text

Edit the zone file.

Update the SOA record serial number.