DNS RECORD GUIDE

SOA record

Describes the authority and synchronization settings of a DNS zone.

What is the SOA record type?

The Start of Authority record identifies the primary nameserver, responsible contact, serial number and timing values.

Common uses

  • Comparing zone versions
  • Diagnosing secondary DNS synchronization
  • Inspecting negative-cache timing

What to enter

Enter the domain representing the DNS zone.

example.com

How to read the result

The serial indicates the zone version. Refresh, retry, expire and minimum TTL values control secondary-server and caching behaviour.

How SOA DNS lookups work

When a client requests a SOA record, it normally asks a recursive DNS resolver. The resolver may return a cached answer or contact the domain’s authoritative nameservers. Cached answers improve speed, but they also explain why a recent DNS change may not appear everywhere at exactly the same time.

DNSReach queries several independent public resolvers and, when possible, the authoritative nameservers for the domain. An authoritative answer reflects the zone currently published by the DNS provider. A recursive answer reflects what that resolver currently knows, which may still be an older cached value until its cache expires.

How to check a SOA record with DNSReach

  1. Open the DNS checker and select SOA.
  2. Enter example.com in the format described above.
  3. Run the check and watch each resolver return independently.
  4. Compare public resolver answers with the authoritative results marked by a shield.
  5. Investigate amber results because they differ from the authoritative or majority answer.
Check SOA now →

Why SOA answers can differ

The most common reason is caching. DNS records have a time to live, and resolvers that cached the previous value can continue serving it until that period ends. Differences can also come from split-horizon DNS, filtering policies, malformed responses, DNSSEC validation failures, resolver outages, or querying a hostname different from the one where the record is actually published.

A failed lookup is not always evidence that the entire domain is broken. “No record” means the requested type was not found at that exact name. A timeout means a resolver did not answer in time, while a refusal means it declined the query. Checking authoritative servers helps distinguish propagation delay from a configuration problem.

Common SOA troubleshooting steps

  • Confirm the exact hostname and record type.
  • Check the authoritative answer before changing the zone again.
  • Allow existing cached answers to expire after a change.
  • Verify that every authoritative nameserver publishes the same zone version.
  • Review provider-specific formatting requirements and remove accidental duplicate records.

SOA record FAQ

What is the SOA record type?

Describes the authority and synchronization settings of a DNS zone.

How do I check SOA records?

Enter example.com in DNSReach, select SOA, and run the check. DNSReach compares public recursive resolvers with available authoritative nameservers.

Why do DNS resolvers show different SOA answers?

Resolvers may hold cached data created at different times. A recent DNS change can therefore appear on some resolvers before others until older cached answers expire.

What does “no record” mean for SOA?

The resolver answered successfully but found no SOA record at the exact name queried. This can be normal when that record type is optional or published at another hostname.

Related DNS record guides