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
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
In article mailman.649.1254472597.14796.bind-us...@lists.isc.org,
Michael Monnerie michael.monne...@is.it-management.at wrote:
On Freitag 02 Oktober 2009 Mark Andrews wrote:
if (set(allow-query-cache))
use allow-query-cache;
else if (set(allow-recursion))
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
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 client
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
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: did
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
Dear list,
I have one client with a specific zone. When the client does a query for
localhost on the nameserver, or a reverse lookup for 127.0.0.1,
everything seems perfectly okay. As soon, as the client tries to lookup
i.e. google.de or any external ip, I am getting query refused errors.
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
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
Have you read the documentation that describes what allow-query does?
varlistentry
termcommandallow-query/command/term
listitem
para
Specifies which hosts are allowed to ask ordinary
DNS questions.
12 matches
Mail list logo