Fix the “SOA serial number format is invalid” error

What “SOA serial number format is invalid” means

The SOA record stores important information about a DNS zone. One of its fields is the serial number.

The serial number acts as the zone’s version number. Secondary DNS servers check that value to decide whether they need to pull updates.

Why the SOA serial number matters

The SOA serial controls zone synchronization. If the value increases correctly, secondaries can detect the changes made and update accordingly.

If the serial value is invalid, some secondaries may keep serving the last correct version until the problem is fixed.

That can leave misconfigured records in place, creating operational issues such as email delivery failures.

SOA serial number formats

There are multiple valid formats for an SOA serial number, although some DNS providers require a specific numbering convention.

The official SOA serial number formats include:

• YYYYMMDDnn
• Unix timestamp
• Simple incrementing integer

Date-based serials are easy to review during routine checks. Timestamps are common in automated environments. Simple incrementing integers work well when updates are manual and infrequent.

Note: The value must stay numeric, fit your provider’s rules, and always move forward.

Common causes of the “SOA serial number format is invalid” error

Formatting issues

Formatting problems are the most common cause of a “SOA serial number format is invalid” error. The serial number may contain letters, spaces, slashes, hyphens, or other separators.

A date-based value can also fail even when it looks numeric. The structure might not match the format your provider expects, or the date portion may be invalid.

Number size

Your SOA serial must stay within the size limits your DNS provider accepts. Problems usually happen when a date-based serial exceeds the allowed length, a Unix timestamp is too long, or a simple incrementing number passes the maximum supported value.

Serial progression issues

A serial number can also be operationally wrong even when the format looks clean. If the new value is lower than the previous one, secondaries won’t update.

Serial numbers are often auto-generated. A misconfigured or outdated DNS panel may generate an incorrect serial number, causing the update to fail.

Step-by-step fix guide

1. Confirm the format your DNS provider expects

Start by reviewing your provider’s dashboard or documentation to confirm whether it expects a date-based serial, a Unix timestamp, or a simple incrementing integer.

Do not assume that a format accepted by one platform will be accepted by another.

2. Make sure the new value is higher than the current value

Query the current SOA record before you make a change. Then choose a new serial that’s higher than the current value and still matches your format.

If you use a date-based pattern such as 2026030601, increment the suffix when you make multiple changes on the same day.

3. Correct the serial so it’s valid and numeric

Remove non-numeric characters. Fix malformed date values. Replace unusual custom formats with a clean numeric value your platform accepts.

Valid example:

2026030601

Invalid example:

2026-03-06-01 2026/03/06 v103

Keep the format simple and accurate.

4. Confirm that secondary DNS servers pick up the new serial

After you publish the corrected value, query the DNS. You want to see the updated serial number. If a server still returns the old serial, the change may not have been completed.

Keep in mind that DNS propagation can take 24 to 48 hours, so some servers may continue returning the previous serial during that window.

5. Reset the serial number if the problem persists

If the serial history is inconsistent, reset it to a clean numeric value, then republish the zone and check the DNS again.