How to fix BIND's journal out of sync error

If you use a BIND name server to dynamically update a zone record (such as a DHCP IP address from a client), things can go awry if you manually update the zone file. Hence : 

zone example.com/IN: journal rollforward failed: journal out of sync with zone
zone example.com/IN: not loaded due to errors.

To clear the error, run BIND in diagnostic mode by executing the following command :

[fedora@ns ~]$ sudo named -g

Once you are satisfied that BIND is starting correctly, stop the running BIND service. 

[fedora@ns ~]$ sudo systemctl stop named-chroot

Remove any '.jnl' files that reside in the zone directory. 

[fedora@ns ~]$ sudo -i
[root@ns ~]$ cd /var/named/chroot/var/named
[root@ns named]$ rm *.jnl

If you have a dynamic zone, it is best to "freeze" the zone first, make the required edits, then "thaw" the zone afterwards to avoid this problem in future. The commands are as follows : 

// sudo rndc (freeze / reload / thaw) [zone] [in [view]]

[fedora@ns ~]$ sudo rndc freeze example.com in trusted

// make the necessary edits to the zone file

[fedora@ns ~]$ sudo rndc reload example.com in trusted
[fedora@ns ~]$ sudo rndc thaw example.com in trusted