Originally Posted by kdelover
am not so good with selinux
all i know is put selinux in permissive mode rather than having it in enforcing or disabled mode.
Disabling SELinux is not the preferred way of dealing with issues. Rather than taking the easy way out, comfortably learning nothing in the process, you could try to understand what the error is about and how to correct it.
Originally Posted by abhijit_mohanta
#============= named_t ==============
allow named_t named_zone_t:dir write;
This would make sense if the Fedora SELinux BIND policy didn't already allow named_t to write to named_zone_t. Odd. See if there's any inactive booleans? Run 'getsebool -a|grep named'. If you like Fedora you should keep up with the release schedule (11 is current now) or choose a distribution with a less demanding update schedule because Fedora 9 is outdated and no longer maintained (if you didn't know).