Me too. The "managed-keys-directory" directive mentioned in comment #7 did not help for me. In my /var/log/messages, there is the following message:
Jun 13 21:32:14 thorin setroubleshoot: SELinux is preventing /usr/sbin/named fro
m write access on the directory /var/named/chroot/var/named. For complete SELinu
x messages. run sealert -l 75f9b442-f638-4f28-9d82-747a09131e2c
Me too. The "managed- keys-directory" directive mentioned in comment #7 did not help for me. In my /var/log/messages, there is the following message:
Jun 13 21:32:14 thorin setroubleshoot: SELinux is preventing /usr/sbin/named fro chroot/ var/named. For complete SELinu f638-4f28- 9d82-747a09131e 2c
m write access on the directory /var/named/
x messages. run sealert -l 75f9b442-
After running
setenforce 0; /etc/init.d/named restart; setenforce 1
my bind no longer eats 100 % of CPU.