Plesk fails to start BIND or resolve on Fedora
As with any strange behavior in Plesk, first run the updater. This will often either correct the problem you're experiencing or update packages that are contributing to the problem.
In some cases, Plesk will give an error when trying to start named (BIND) from the services page. Check /var/log/messages after attempting to start and look for errors indicating that bind can't load files from /var/named because they're missing (not found). If you find these messages, the problem is most likely because of bind-chroot.
The bind-chroot package starts BIND in a chroot jail, limiting the security risk should bind be breached. This creates a fake root directory exclusively for BIND in /var/named/run-root. When BIND is started, /var/named/run-root is mapped to / and BIND sees the contents as the root directory. This is why BIND can't find files that's looking for: Plesk is putting them in the real /var/named. To confirm that bind-chroot is installed, do 'rpm -qa|grep chroot'. To fix the problem do 'rpm -ev '. Then, try to start named from the Plesk Services page.
Once this is complete, you may need to go into the DNS for each domain and hit "Switch" twice to resave the zone configs