Fedora 12 / BIND 9 / ISPConfig 3

Discussion in 'Installation/Configuration' started by ferra, Jul 2, 2010.

  1. ferra

    ferra Member

    here is how we configured Bind9 on Fedora 12 with ISPConfig 3:

    (Don't forget to uninstall any other DNS service)

    To install a chrooted BIND9, we do this:
    yum install bind-chroot
    Then do this:
    chmod 755 /var/named/
    chmod 775 /var/named/chroot/
    chmod 775 /var/named/chroot/var/
    chmod 775 /var/named/chroot/var/named/
    chmod 775 /var/named/chroot/var/run/
    chmod 777 /var/named/chroot/var/run/named/
    cd /var/named/chroot/var/named/
    ln -s ../../ chroot

    cp /usr/share/doc/bind-9.6.2/sample/var/named/named.local /var/named/chroot/var/named/named.local
    cp /usr/share/doc/bind-9.6.2/sample/var/named/named.localhost /var/named/chroot/var/named/named.localhost
    cp /usr/share/doc/bind-9.6.2/sample/var/named/named.ca /var/named/chroot/var/named/named.ca

    cp /usr/share/doc/bind-9.6.2/sample/var/named/named.empty /var/named/chroot/var/named/named.empty
    cp /usr/share/doc/bind-9.6.2/sample/var/named/named.loopback /var/named/chroot/var/named/named.loopback

    touch /var/named/chroot/etc/named.conf.local

    cat /var/named/chroot/etc/named.conf

    // named.conf
    // Provided by Red Hat bind package to configure the ISC BIND named(8) DNS
    // server as a caching only nameserver (as a localhost DNS resolver only).
    // See /usr/share/doc/bind*/sample/ for example named configuration files.
    options {
    listen-on port 53 {; };
    listen-on-v6 port 53 { ::1; };
    directory "/var/named/chroot/var/named";
    dump-file "/var/named/chroot/var/named/data/cache_dump.db";
    statistics-file "/var/named/chroot/var/named/data/named_stats.txt";
    memstatistics-file "/var/named/chroot/var/named/data/named_mem_stats.txt";
    allow-query { localhost; };
    recursion yes;
    logging {
    channel default_debug {
    file "data/named.run";
    severity dynamic;
    zone "." IN {
    type hint;
    file "named.root";
    include "/var/named/chroot/etc/named.conf.local";

    Let me know if there is anything wrong or where we can improve.

    A big problem is, if a client do a bad configuration on a DNS record, named will not start do to errors.

    On ISPConfig administration, Monitor, still have myDNS-Server offline, there is no Monitor for Bind9 (named service).

    If you want to configure a type slave zone you have to do it using the command line.
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    About which kind of records are you talking?

    The monitor works for bind and mydns. If it shows the service offline, then you dont run a service on localhost on the dns port.

    Not if you use ispconfig, as ispconfig has its own mirroring mechanism.
  3. ferra

    ferra Member

    I have removed myDNS and still have myDNS-Server offline.
    Installed BIND9, and there is no reference to BIND9 on the Monitor

    The type slave zone is when I have a type master in other server (ISP server, for example) and by ISP rules I need to have a slave configured in a different server.

    For example, if a user deletes the NS records the service named will not start, saying zone example.tds/In: has no NS records
    Named Failed to start

Share This Page