Koenraad, Le 13.08.2010 à 13:08, Koenraad Lelong a écrit :
I use a dynamic DNS, i.e. I want the dhcp-server to update the master's dns-server's records. Then this master updates the slave's records. This worked fine but now the update does not work anymore. I found out when I tried to create a static record. I restarted both the dhcp-server and the dns-servers. On the master I got this message : named[23503]: zone 168.192.in-addr.arpa/IN: journal rollforward failed: journal out of sync with zone named[23503]: zone ace-electronics.be/IN: journal rollforward failed: journal out of sync with zone
Actually this is the second time I get this, last time a few months ago. Then I just deleted the journal-files and restarted the dns-server. I could do this again, but I wonder if there's a better way to restore the updates. And important : why would this happen ?
Any hints ?
A mismatch with the journal is inevitable, if you modify the zone files directly. You need to modify the zones through the protocol layer, using the "nsupdate" tool. The nsupdate tool has a very complicated syntax, and 5 years go I wrote a wrapper script that makes it easy to use; should you have a need for frequent modifications, I can provide it. Your other option is to simply modify the zone (file) with an editor, ruthlessly remove the journal files and reload the server. It is useful to flush the journal before doing that ("rcnamed reload" should do it), so the zone files will be in sync with the state cached in memory. If you forget to remove the journal and reload the server, there is a good chance that the name server will silently stop serving the zone later. Which is probably how you ran into the bug, and then you saw the lines in the log. Peter