networkutils.org

Home / DNS Tools / SOA & Serial

SOA & Serial

DNS Tools

Compare serials across authoritative name servers.

Run this tool: the interactive SOA & Serial loads here (requires JavaScript). Input: Domain — e.g. example.org.

Description

The SOA & Serial tool retrieves the Start of Authority record from every authoritative name server for a domain and compares the serial numbers to confirm that all servers are in sync after a zone edit.

Features

✓ SOA record from every authoritative name server
✓ Serial-number comparison across all NS
✓ TTL, refresh, retry and expiry display
✓ Primary master and admin contact

How to Use

Enter a domain name (example.org) and run the tool. The probe queries each authoritative name server for its SOA record and compares the serials.

Input: Domain — e.g. example.org.

Understanding the Results

The output lists each name server with its SOA serial, refresh, retry, expiry and minimum TTL. The summary reports whether all serials agree. Mismatched serials mean one or more secondaries have not yet transferred the latest zone — a common cause of inconsistent DNS answers across resolvers.

Common Use Cases & Examples

→ Confirm all authoritative servers are in sync after a zone edit.

→ Find a lagging secondary causing inconsistent DNS answers.

→ Verify SOA timing values match your operational requirements.

→ Diagnose a split-horizon or multi-provider DNS inconsistency.

Frequently Asked Questions

What does a mismatched SOA serial mean?

It means one or more authoritative name servers are serving an older copy of the zone than the primary. Until they complete a zone transfer, resolvers hitting those servers get stale answers, causing inconsistent behaviour for different users.

How does a secondary know to transfer a new zone?

It polls the primary every refresh interval and compares serials; if the primary’s serial is higher it initiates a transfer. For faster propagation, the primary can send a NOTIFY immediately after a change.

What are refresh, retry and expiry for?

Refresh is how often the secondary checks the primary; retry is the interval after a failed check; expiry is how long the secondary will keep serving the zone if it cannot reach the primary before it stops answering entirely.

About this tool

Maintained by
networkutils.org editorial team
Last updated
September 2026
Testing methodology
DNS queries run through Node.js dns.promises and, for DNSSEC record types (DS/DNSKEY) and the AD validation flag, through Cloudflare DNS-over-HTTPS (application/dns-json). The Propagation Check queries 10 public recursive resolvers directly and compares their A-record answers. The DNS SuperTool performs its checks client-side in your browser over DNS-over-HTTPS using Cloudflare and Google.
Technical references
RFC 1035 — DNS Implementation (SOA)