problem setting up private and public addresses in BIND9.2

[stfaprc]

I'm having a problem setting up a 'two-in-one' DNS for our company , running BIND9.2

the named.conf file has in it:

zone "." {
type hint;
file "named.cache";
};

zone "0.0.127.IN-ADDR.ARPA" {
type master;
file "ourcompany.local";
};

zone "2.22.6.IN-ADDR.ARPA" {
type master;
file "ourcompany.rev";
};

zone "ourcompany.com" {
type master;
file "bftx";
also-notify {
2.111.65.2;
2.171.16.2;
2.171.9.2;
};
};

view "internal" {
match-clients { internals; };
zone "bftx.com" {
type master;
file "/var/named/bftx.local";
};
};


Why is it bombing with an error of :
"when using 'view' statements, all zones must be in views"

when it hits the view section ?

 

[jyorgey]

If you are using only one view statement then all the zones must be included in that view, otherwise you will have to create an additional view for the external view, but either way when you use views all your zones have to be inside a view.

 

[stfaprc]

Thanks for the reply.
I seem to be missing/skipping a step in the docs.
a view needs to be setup for external users,
how am I supposed to setup the access control so that
'match-clients' in the external view rejects internal ip's and only accepts non-internal ip's ?