You could create a script, say that would overwrite the file and use the current unix timestamp in the serial.
all zones would then by inclusion have their serials incremented.
Googling around for answers, I found the following explanation: Serial numbers in DNS zone files provide a way for the server to verify that the contents of a particular zone file are up-to-date.
Based on what I have read I think the problem is that the SOA Serial numbers don't match between the primary server and the secondary servers: Am I correct in this assumption?
If so can I simply manually change the SOA serial number on the primary zone to something like 2476.
A nice HOWTO about this is at: is also the recommended way in the DNS & BIND book (2006 ed.).
Welcome to Linux Questions.org, a friendly and active Linux Community. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration.