<?xml version="1.0" encoding="UTF-8"?><!-- generator="bbPress" -->

<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
>

<channel>
<title>DomainGurus Forums Topic: Plesk fails to start BIND or resolve on Fedora</title>
<link>http://forums.domaingurus.com/</link>
<description>Our Community</description>
<language>en</language>
<pubDate>Fri, 10 Sep 2010 04:52:44 +0000</pubDate>

<item>
<title>admin on "Plesk fails to start BIND or resolve on Fedora"</title>
<link>http://forums.domaingurus.com/topic/plesk-fails-to-start-bind-or-resolve-on-fedora#post-147</link>
<pubDate>Sun, 14 Jun 2009 15:39:06 +0000</pubDate>
<dc:creator>admin</dc:creator>
<guid isPermaLink="false">147@http://forums.domaingurus.com/</guid>
<description>&#60;h1&#62;Plesk fails to start BIND or resolve on Fedora&#60;/h1&#62;
&#60;p&#62;
&#60;/p&#62;&#60;p&#62;As with any strange behavior in &#60;strong&#62;Plesk&#60;/strong&#62;, first run the updater. This will often either correct the problem you're experiencing or update packages that are contributing to the problem.&#60;/p&#62;
&#60;p&#62;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.&#60;/p&#62;
&#60;p&#62;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&#124;grep chroot'. To fix the problem do 'rpm -ev '. Then, try to start named from the Plesk Services page.&#60;/p&#62;
&#60;p&#62;Once this is complete, you may need to go into the DNS for each domain and hit &#34;Switch&#34; twice to resave the zone configs&#60;/p&#62;</description>
</item>

</channel>
</rss>
