Help & Troubleshooting
SOA Record
What this is
The SOA (Start of Authority) record carries the zone's administrative metadata: the primary nameserver, the responsible contact, a serial number that increments with every change, and the timers that control how secondary servers refresh and how long negative answers are cached.
How to read your result
You rarely need to act on SOA values directly. The serial number is the most useful field: comparing it across nameservers tells you whether they are in sync. Sane timer defaults are fine for almost everyone.
Common problems and how to fix them
Serial number differs between nameservers
How it shows up: Some users get updated records while others get stale ones for far longer than the TTL explains.
How to fix it: A secondary server is failing to transfer the zone from the primary. Check zone-transfer (AXFR/IXFR) settings and connectivity between the servers, or let your managed DNS provider know — with managed DNS this should never happen.
Negative-cache TTL (minimum) set very high
How it shows up: After adding a brand-new record, resolvers that already asked for it keep answering "does not exist" for hours.
How to fix it: Lower the SOA minimum/negative-TTL field to something like 300–3600 seconds so mistakes and new records recover quickly.