Linux Bind: Difference between revisions
(Created page with "Category:Linux === Errors === ==== journal rollforward failed: journal out of sync with zone ==== Editing zone files without stopping dhcp updates will cause your current...") |
No edit summary |
||
Line 1: | Line 1: | ||
[[Category:Linux]] | [[Category:Linux]] | ||
=== Errors === | === Errors === | ||
==== zone file not loading due to could not create jnl file ==== | |||
This is directory permissions issue. | |||
Check the directory permissions for bind (/etc/bind) to make sure that the user bind has rw permissions. | |||
# ls -la /etc/ | grep bind | |||
drwxrwsr-- 2 root bind 4096 Mar 18 00:58 bind | |||
I found that on Debian Wheezy 7.8, the default permissions on the directory were causing the error. | |||
drwxr-sr-- 2 root bind 4096 Mar 18 00:58 bind | |||
chmod'ing the directory fixed it: | |||
# chmod 764 /etc/bind | |||
You could also chown the directory recursively, but I try to give the least amount of permissions as possible for it to run. | |||
# chown -R bind:bind /etc/bind | |||
==== journal rollforward failed: journal out of sync with zone ==== | ==== journal rollforward failed: journal out of sync with zone ==== | ||
Editing zone files without stopping dhcp updates will cause your current zone that you are working to stop working... restarting the process and rebooting have no affect. | Editing zone files without stopping dhcp updates will cause your current zone that you are working to stop working... restarting the process and rebooting have no affect. |
Latest revision as of 00:34, 18 March 2015
Errors
zone file not loading due to could not create jnl file
This is directory permissions issue.
Check the directory permissions for bind (/etc/bind) to make sure that the user bind has rw permissions.
# ls -la /etc/ | grep bind drwxrwsr-- 2 root bind 4096 Mar 18 00:58 bind
I found that on Debian Wheezy 7.8, the default permissions on the directory were causing the error.
drwxr-sr-- 2 root bind 4096 Mar 18 00:58 bind
chmod'ing the directory fixed it:
# chmod 764 /etc/bind
You could also chown the directory recursively, but I try to give the least amount of permissions as possible for it to run.
# chown -R bind:bind /etc/bind
journal rollforward failed: journal out of sync with zone
Editing zone files without stopping dhcp updates will cause your current zone that you are working to stop working... restarting the process and rebooting have no affect.
If you stop bind and start it with named -g and see the following:
zone somedomain.com/IN: journal rollforward failed: journal out of sync with zone
You saved an edit during an update and the journal became out of sync.
This can be remedied by executing the running the following commands:
rndc freeze somedomain.com rndc reload somedomain.com rndc thaw somedomain.com
If this does not fix the issue, then you can shut down bind and delete the journal it was complaining about.
Finally, you should freeze the zone, edit, reload, and thaw when making changes on a DDNS setup.
rndc freeze somedomain.com
<editor of choice - vi,nano,emacs> somedomain.com and make your changes; then:
rndc reload somedomain.com rndc thaw somedomain.com