>> On 01.10.09 19:10, Sven Eschenberg wrote:
>>> Funny enough, I did not have any allow-query at all, but adding
>>> allow-query {any;} did indeed change the behavior. But
>>> allow-query-cache obviously defaults to localhost, localnets and was
>>> triggering the behavior that confused me.
Matus UHLAR - fantomas schrieb:
On 01.10.09 19:10, Sven Eschenberg wrote:
Funny enough, I did not have any allow-query at all, but adding
allow-query {any;} did indeed change the behavior. But allow-query-cache
obviously defaults to localhost, localnets and was triggering the
behavior that
In article ,
Michael Monnerie wrote:
> On Freitag 02 Oktober 2009 Mark Andrews wrote:
> > if (set(allow-query-cache))
> > use allow-query-cache;
> > else if (set(allow-recursion))
> > use allow-recursion;
> > else if (set(allow-query))
> >
On Freitag 02 Oktober 2009 Mark Andrews wrote:
> if (set(allow-query-cache))
> use allow-query-cache;
> else if (set(allow-recursion))
> use allow-recursion;
> else if (set(allow-query))
> use allow-query;
> else if (se
In message <200910011237.09...@zmi.at>, Michael Monnerie writes:
> On Donnerstag 01 Oktober 2009 Mark Andrews wrote:
> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Specifies which hosts are allowed to =
> get answers
> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 from the cache. =A0If
> > allow-query-cache is n
On 01.10.09 19:10, Sven Eschenberg wrote:
> Funny enough, I did not have any allow-query at all, but adding
> allow-query {any;} did indeed change the behavior. But allow-query-cache
> obviously defaults to localhost, localnets and was triggering the
> behavior that confused me.
OK, again: d
Funny enough, I did not have any allow-query at all, but adding
allow-query {any;} did indeed change the behavior. But allow-query-cache
obviously defaults to localhost, localnets and was triggering the
behavior that confused me.
Inbetween I overhauled the config, setting all the options expli
On 30.09.09 15:59, Sven Eschenberg wrote:
> When I had no allow-query statement at all in my config, everything
> worked find (includign recursion) for all clients, that were in subnets
> directly attached to the server. The external view (authoriative, non
> recursive) did work for every cli
On Donnerstag 01 Oktober 2009 Mark Andrews wrote:
> Specifies which hosts are allowed to get answers
> from the cache. If
> allow-query-cache is not set then
> allow-recursion is used if set, otherwise
> allow-query is used if set unless
> recursion no; is set i
Have you read the documentation that describes what allow-query does?
allow-query
Specifies which hosts are allowed to ask ordinary
DNS questions. allow-query may
also be specified in
Dear list,
This seems more tricky, then I thought.
When I had no allow-query statement at all in my config, everything
worked find (includign recursion) for all clients, that were in subnets
directly attached to the server. The external view (authoriative, non
recursive) did work for every cl
I got it fixxed with an allow-query statement.
But this arises another question: Does bind implicitly add allow-queries
for locally attached interfaces and the networks configured for these?
I am asking, because it used to work for all the subnets directly
attached to the machine.
Regards
12 matches
Mail list logo
