We’ve seen several folks run into this after upgrading to CentOS 5.2 from 5.1. Somehow the configuration of BIND is changed to no longer chroot BIND.
Turn chroot back on in BIND, and things should come back into sanity. I have no idea why the upgrade broke things, but it’s not really related to Virtualmin. It’d be a bug in RHEL/CentOS, though I haven’t had luck finding any discussion of it.
I’m still running CentOS Linux 4.6, I have not done any upgrading.
A stupid question, wher and how to “turn chroot back on in BIND”, are that BIND path I have to change, It seems to bee a wrong path of some reason there.
Joe!
This happend when I create a new virtuel server.
In BIND DNS-server the new created server are there as a master zon, but all my other server are still not there.
My question are If I need to create a new master zon for all my missing server/domain.
I need to get this peoblem solved, so I’m able to do my daily backup of domain, so please Joe what should I do?
I don´t understand that you say about "Turn chroot back on in BIND"!