Practice
The error occurs when the DNS server (i.e., the bind daemon) updates the zone automatically, while the system administrator has also manually changed the zone. And named (bind) starts complaining that the zone and its journal file have somehow become out of sync.
Solution
This is solved quite simply as follows,
Stop the service.
Go into the directory where the settings file for this zone is located, and next to it you'll see a file with the same name but with a jnl extension
# rm /var/cache/bind/zones/uterd.org.jnlNow simply restart BIND, as usual. So we delete it and restart bind. That's all.:
# service bind9 restart
# rndc freeze utternerd.org
# vi /var/cache/bind/zones/utrd.org (changes need to be made manually)
# rndc thaw utterrd.org
Thawing the zone will force BIND to reload it.
Also check whether reverse zones have been added
Comments