How to fix: SOA Refresh Interval Too High
The SOA refresh interval is above 24 hours. This slows propagation of zone changes to secondary nameservers, increasing the time it takes for NS record updates to take effect.
Why it matters
During incident response or planned NS rollover, stale secondary nameservers continue serving old data for up to the refresh interval, delaying changes and potentially causing resolution failures.
The SOA refresh value tells secondary nameservers how often to check the primary for zone updates. A value above 86400 seconds (24h) means secondaries may serve outdated zone data for a full day after a change.
How to fix it
- 1Lower the refresh interval to 3600-7200 seconds for zones that change frequently.
- 2Verify your SOA: dig SOA example.com
Code examples
DNS zone file SOA
example.com. IN SOA ns1.example.com. hostmaster.example.com. (
2024010101 ; serial
3600 ; refresh (1 hour)
900 ; retry (15 min)
604800 ; expire (1 week)
300 ; negative TTL (5 min)
)Check SOA
dig +short SOA example.comReferences
Detected automatically by VulnRadar. The check id is dns-soa-refresh-high, stable across every scan so you can filter or diff on it.
More dns checks
Questions
- How severe is SOA Refresh Interval Too High?
- VulnRadar rates this low severity in the dns category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id dns-soa-refresh-high, which stays the same between runs so you can filter, diff, or gate CI on it.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.