Hello, World, Sorry for the silence - I was busy with other stuff, but now I would like to inform you about recent changes in SOA serial updating algorithm.
Statement: Zone transfer to zone slave(s) will, in the event of zone file changes, occur only if the serial number of the SOA RR is arithmetically greater that the previous one (as defined by RFC 1982). >From here: http://www.zytrax.com/books/dns/ch9/serial.html Existing issues in current stable 2.1.5 version: 1st issue: serial updating when revision nr. reaches it's limit (99): It works unless you will require to make more than 99 changes - after it will always (on the same day) return the same serial. That means that zone will be not updated on slave server. It's hard to believe that there could be more than 99 changes per one day, but at least Poweradmin will know how to deal in such situation. How it was fixed - date which is used in serial will be updated (to the next day), revision number will have 00 value. An example: serial=2011052699, today's date=20110526, next serial=2011052700 2nd issue: serial updating when existing date (extracted from serial) is in the future: Yes, that is possible in our imperfect world, therefore now Poweradmin will use date from serial and just increment revision number. An example: serial=2011052705, today's date=20110526, next serial=2011052706 All these changes probably will make your life easier. Your comments are welcome. For more details check 535-542 commits (if you can read PHP code). --Edmondas _______________________________________________ poweradmin-users mailing list [email protected] http://lists.poweradmin.org/cgi-bin/mailman/listinfo/poweradmin-users
