Two-in-one DNS server with BIND9 - all zones must be in views

Discussion in 'HOWTO-Related Questions' started by c4rdinal, Apr 2, 2008.

  1. c4rdinal

    c4rdinal New Member

    First of all thank you for the Howto!

    I would like to ask something about my bind logs as follows:

    tail -f /var/log/syslogd

    Apr 3 02:54:27 deneb named[27976]: /etc/bind/named.conf:10: when using 'view' statements, all zones must be in views

    What does it mean and how to resolve it?
    I can ping external sites as well as internal but what does the log is about?

    Also,

    Linux:~# named-checkzone example.com db.example
    zone example.com/IN: loading master file db.example: file not found

    How can I fix it?

    TIA
     
  2. topdog

    topdog HowtoForge Supporter

    The first error means that all your zones need to be in the view declaration

    Code:
    view "viewname" {
    
    
    }
    Second error means named cannot find your zone file
     
  3. c4rdinal

    c4rdinal New Member

    Hi!

    Here's what I included in my /etc/bind/named.conf.local

    view "internal" {
    match-clients { internals; };
    recursion yes;
    zone "domain1.com" {
    type master;
    file "/etc/bind/zones/internal/db.domain1";
    };
    };

    view "external" {
    match-clients { any; };
    recursion no;
    zone "domain1.com" {
    type master;
    file "/etc/bind/zones/external/db.domain1";
    allow-transfer { slaves; };

    };
    zone "domain2.com" {
    type master;
    file "/etc/bind/zones/external/db.domain2";
    allow-transfer { slaves; };
    };

    I have 2 external domains and 1 internal. Should I include in the view my reverse zones?

    Thanks alot.
     
  4. topdog

    topdog HowtoForge Supporter

    If you are using views all your zones should be within a view.
     

Share This Page