Recent versions of Named are weird

[Red Squirrel]

On my online dedicated server (CentOS 6.5) I noticed that any time named fails to load due to a syntax error or other reason, it DELETES ALL CONFIG files in /var/named/chroot. I need to then restore from backup. That's one issue. I've never seen this before.

On a completely different CentOS 6.5 server, I notice there is a chroot within a chroot, and it insists on using the 2nd one. Ex: any files I include, it wants them to be in there. Why is it doing this?

Is there a way or getting rid of the second chroot? Ex:

/var/named/chroot/var/named/chroot

I added my zone config file to /var/named/chroot/var/named/ and the zone files in the zones folder but it's complaining that it can't find the individual zone files because it actually wants them to be in the 2nd chroot folder.

This is rather messy, I don't want to do it this way, I've never had to do it this way. Is there a way to fix this?

 

[Red Squirrel]

...and it seems to have fixed itself after a few restart attempts, and fixing some zone errors. Weird. Still unsure why on the other server it completely deletes all the config though, that is a more scary issue, but I don't even really want to touch that server. It's not often I have to add new zones or make changes. Every time I have to restart the service it's a risk of taking out my entire web infrastructure because of that annoying bug.