SOA Record Lookup Tool

Check SOA records instantly across multiple global resolvers to validate your zone's authority and serial number.

How to troubleshoot DNS zone health with an SOA Lookup

The SOA record is the master header of your DNS zone. It contains critical information about how your DNS servers interact. Enter your domain above to query its Start of Authority record. This is especially useful for tracking if your DNS updates have reached a specific resolver by checking the Serial Number.

Interpreting your SOA results

  • Serial Number Tracking: This is the version number of your DNS zone. Every time you make a change, the serial should increase. If one resolver shows a lower serial than another, it is still holding an outdated version of your records.
  • Primary Nameserver: The SOA record identifies the main nameserver where your zone file originates. All other secondary nameservers look to this server for updates.
  • Refresh & Retry Timers: These values (in seconds) tell secondary nameservers how often they should check for updates. If these are set too high, propagation of changes will take longer.
  • Negative Cache TTL: This value tells resolvers how long they should remember that a record doesn't exist. High values here can cause "ghost" errors to linger after you've fixed a missing record.

SOA record lookup for zone health and timers

The SOA record describes authoritative zone metadata, including the primary name server and the zone serial. It also defines timing values for refresh, retry, expire, and minimum TTL. A SOA lookup is useful to verify zone transfers, debug propagation, and confirm that a migration updated the serial number.

Common SOA issues include stale serial numbers, incorrect RNAME (responsible email) values, or inconsistent SOA data across name servers. If your zone uses dynamic updates, the serial should increase with each change. The timers can also affect how quickly secondary name servers pick up updates.

If you need related checks, try Check NS record online and Check DNSSEC lookup online.

The serial indicates the zone version. Secondaries use it to decide whether to pull updates. If the serial does not change, updates may not propagate to secondaries.

RNAME represents the admin email for the zone, with the first dot replaced by an at symbol. For example hostmaster.example.com means hostmaster@example.com.

Refresh controls how often secondaries check for updates. Retry defines how soon to retry after a failed refresh.

Historically it was used for negative caching. Modern DNS uses it for negative response TTL, indicating how long NXDOMAIN responses can be cached.

It indicates propagation issues among authoritative servers. Verify that all secondaries can transfer and that the serial is consistent.

Mostly no. It is primarily used by DNS infrastructure and administrators, but it can impact caching and update behavior.