s and implement it. It doesn't really help either
that every environment that I will deal with will be NAT'ed so I have to take
extra care with that also!
Regards,
Kaya
-Original Message-
From: Kevin Darcy
To: bind-users@lists.isc.org
Sent: Thu, Jul 2, 2009 2:36 am
d/db.root";
};
};
Then later I could build another view once my network grows over the
internet without taking into consideration VPN's for the moment:
view "trusted_wan" {
match-clients { IP1; IP2; !192.168.0.0/22; !127.0.0.1; };
allow-recursion { 127.0.0.1; };
include &
7;s for the moment:
view "trusted_wan" {
match-clients { IP1; IP2; !192.168.0.0/22; !127.0.0.1; };?
allow-recursion { 127.0.0.1;? };
include "/etc/opt/csw/bind/named.conf.external";
zone "." {
type hint;?
file "/etc/opt/csw/bind/d
The first view matched is the one which is selected.
External clients are matching the "external" view, but they are not
allowed to recurse. Therefore they can only see the root zone and/or
whatever authoritative zones you've defined in that "include" file.
Note that the "all" view is *never*
Hi, this is my first post here and I have quite an interesting problem at that!
I have migrated my DNS service from Debian Etch Linux to Sun Solaris 9 running
the Blastwave version of Bind9.
This is a bit hard to explain but basically as default DNS setup in Debian, it
installs root servers in
5 matches
Mail list logo
