Technical article 117442

My slave nameserver is failing to update its zone files and is getting an error message in the syslog.

OpenServer 5.0.5OpenServer 5.0.6UnixWare 7.0.0UnixWare 7.0.1UnixWare 7.1.0UnixWare 7.1.1Open UNIX 8

Written · Last revised

Problem

The system is set up properly as a slave nameserver. But, the zone transfers from the master are not happening and something similar to the following is populated in syslog:

named[12342]: Zone "foo.com" (class 1) SOA serial# (2500000000) rcvd from [10.10.10.11] is < ours (1000000)

Solution

It would seem that the zone transfer should be initiated as the number 2500000000 is definitely not less than 1000000. However, BIND uses sequence space arithmetic which means that for any serial number, half the numbers in the number space (32-bit unsigned integer) are larger and half are smaller. So, you can have a larger number evaluate as being smaller as in the example above.

You will need to either:
- On the slave server(s):
       - remove the appropriate zone files
       - restart the name server
OR:
- On the master server(s):
       - change the serial number in the master's files so that it
         evaluates to being greater than the current serial number on
         the slave and wait for the slave(s) to pick up a new copy

Quoted from "DNS and BIND" (O'Reilly & Associates, September, 1998):

Let's go over an example of sequence space numbers. Suppose the serial number is 5. Serial numbers 6 through (5 + 2,147,483,647) are larger than serial number 5. Serial numbers (5 + 2,147,483,649) through 4 are smaller serial numbers. Notice that the serial number wrapped around to 4 after reaching 4,294,967,295. Notice also that we didn't include the number (5 + 2,147,483,648) because this is exactly halfway around the number space, and it could be larger or smaller than 5, depending on the implementation. To be safe, don't use it.

Now back to the original problem. If your zone serial number is 25, 000 and you want to start numbering at 1 again, you can speed through the serial number space in two steps. First, add the largest increment possible to your serial number (25,000 + 2,147,483,647 = 2,147,508,647). If the number you come up with is larger than 4,294,967,295 (the largest 32-bit value), you'll have wrap around to the beginning of the number space by subtracting 4,294,967,296 from it. After changing the serial number, you must wait for all of your secondaries to pick up a new copy of the zone. Second, change the zone serial number to its target value (1), which is now larger than the current serial number (2,147,508,647). After the secondaries pick up a new copy of the zone, you're done!

NOTES:    Sequence space arithmetic is discussed in more depth in RFC1982.

See also

"DNS and BIND" RFC1982

From the Xinuos technical article database, record 117442. Reproduced with permission. The original is at www.sco.com/ta/117442, which is reachable but blocked from search engines.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.