> The documentation for `match-clients' isn't comprehensive enough... Can
> I add all host from, for example 172.16/16 except a single host? Does:
>
> match-clients { 172.16.0.0/16;!172.16.1.1; }
BIND checks the ACL in the order you specify. In your example,
172.16.1.1 will be allowed by the firs
On 25/11/2011 23:36, Marek Kozlowski wrote:
> One more question:
> The documentation for `match-clients' isn't comprehensive enough... Can
> I add all host from, for example 172.16/16 except a single host? Does:
>
> match-clients { 172.16.0.0/16;!172.16.1.1; }
List the exception first, otherwise
:-)
One more question:
The documentation for `match-clients' isn't comprehensive enough... Can
I add all host from, for example 172.16/16 except a single host? Does:
match-clients { 172.16.0.0/16;!172.16.1.1; }
form an AND or an OR?
Best regards,
/m
_
On 25/11/2011 16:59, Marek Kozlowski wrote:
> Is it allowed to use a few `zone' clauses for a single domain? Is
> something like this correct:
>
> zone "mickey.mouse.com" in {
> type master;
> file "pri/mickey-public.zone";
> allow-query { any; };
> allow-transfer {
> Do I *have* to use views to deal with such distinction or can I specify
> it just as above without views?
You have to use views so that the server can decide which clients get
which responses. This you specify in a match-clients {} stanza within
the view.
-JP
__
On Fri, Nov 25, 2011 at 11:59 AM, Marek Kozlowski
wrote:
> Do I *have* to use views to deal with such distinction or can I specify
> it just as above without views?
Pretty sure you have to use views, in the least doing so would likely
be the best good practice to follow.
--
aRDy Music and Ric
:-)
Forgive me a stupid question but I can't find the answer...
Is it allowed to use a few `zone' clauses for a single domain? Is
something like this correct:
zone "mickey.mouse.com" in {
type master;
file "pri/mickey-public.zone";
allow-query { any; };
allow-trans
7 matches
Mail list logo
