Hi all, <p> If you're planning to install, or currently attempting to install, Virtualmin Professional on Fedora Core 6, be aware that the current bind packages do not create a named.conf, which is just too much craziness for our poor installer to comprehend...this one missing file causes quite a bit of havoc for the remainder of the installation. <p> So, we need to make sure there is a sane named.conf to work with before the installation begins. Here's how: <p> yum install bind bind-chroot caching-nameserver <p> cd /var/named/chroot/etc<br> cp named.caching-nameserver.conf named.conf <p> Now you can run the installation. <p> If you've already been bitten by this particularly annoying quirk of the Fedora Core 6 bind package, and have a botched Virtualmin installation on your hands, you can re-run the bits you need. This assumes your install ended with INFO messages only, and an installation completed message--if it ended with any FATAL level errors, drop me an email and I'll help you get it resolved. This workaround will not fix any FATAL errors! <p> Ok, on to the "fix things" process: <p> rpm -e --nodeps virtualmin-base<br> yum install virtualmin-base <p> During this step, you should see a number of "Configuring Virtualmin", "Configuring Postfix", etc. messages. These will be followed by a list of firewall ports being opened in the default firewall. If any errors occur, let me know and I'll tell you how to resolve them. <p> This problem will be automatically detected in the next version of the virtualmin-base package, and the workaround will occur automatically. There is a bug about this problem already filed in the Red Hat bugzilla, here: <p> <a href="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=216075">https://bug... <p> Sorry for any inconvenience anyone has experienced attempting to install on Fedora Core 6, since this buggy bind update was rolled out by Fedora. Feel free to ask for help. When things go wrong with install.sh, there's no charge for the installation service.