Actually, I just realized a possible counterexample: if the zone is a
subzone of another zone that the server hosts, the type of error
depends
on the strategy used. With the zone statement, the error will be
REFUSED; without the zone statement, it will be SERVFAIL because of
the
lame
On Jan 17, 2012, at 3:44 AM, Matus UHLAR - fantomas wrote:
Whether you set allow-query to none, or remove the zone statement,
clients will get an error when they try to query the zone.
On 17.01.12 14:13, Jeff Peng wrote:
There is a difference when you develop a web interface for DNS
I would use
allow-query { 127.0.0.1; };
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
On 16.01.12 14:50, Jeff Peng wrote:
If I just want to disable any client to query for a zone, but keep
that zone in the config file (maybe later I will enable it to be
accessable), can I just set:
allow-query { none; };
in the zone section?
afaik you can. According to docs, you can use
?
Would cut down on memory usage, load time, etc…
I'm sure you have a use case, just a wondering…
W
allow-query { none; };
in the zone section?
zone example.com {
type master;
file example.com.db;
allow-query { none; };
};
Thanks
于 2012-1-17 1:58, Warren Kumari 写道:
Just out of interest, why wouldn't you just comment out the zone stanza?
Would cut down on memory usage, load time, etc…
I'm sure you have a use case, just a wondering…
Well, my dns manage system (dnsbed.com) requires a zone pause feature.
When user click
Hi,
If I just want to disable any client to query for a zone, but keep that
zone in the config file (maybe later I will enable it to be accessable),
can I just set:
allow-query { none; };
in the zone section?
zone example.com {
type master;
file example.com.db;
allow-query { none
7 matches
Mail list logo
