Hey, there is actually a slight ambiguity in the specification there, after all you could be referring to the serial number as used in the DNS or the ascii characters representing that serial number in the record.
Those would have different numbers of '1' bits. Are there two valid solutions or just one?
Now you have me worried :)
"SERIAL The unsigned 32 bit version number of the original copy of the zone. Zone transfers preserve this value. This value wraps and should be compared using sequence space arithmetic. "
Whereas the other says:
"Serial numbers may be incremented by the addition of a positive integer n, where n is taken from the range of integers [0 .. (2^(SERIAL_BITS - 1) - 1)]. For a sequence number s, the result of such an addition, s', is defined as
s' = (s + n) modulo (2 ^ SERIAL_BITS)
"and
" Addition of a value outside the range [0 .. (2^(SERIAL_BITS - 1) - 1)] is undefined."
Where SERIAL_BITS apparently is the 32 from the other RFC.
So you can add serial numbers as long as they're below or equal to 0x7fffffe but the result of the addition is still a valid serial number, and you can happily increment past 0x7ffffffe only you're no longer allowed to add that number to another serial number.
http://tools.ietf.org/html/rfc1982
Interesting.