You also have these acl's, which I find quite useful:
allow-query {acl-list}
allow-query-cache {acl-list}
allow-recursion {acl-list}
As I recall, all of them are valid inside a view.
You could also try to throw in some debug logging.
Here is what I do for troubleshooting:
#> rndc querylog
#> r
Am 28.07.2011 01:18, schrieb Bob:
> These two views are identical in any way I can see, so the fault may
> be in an included configuration file that is not included in your
> message.
>
> Look for allow-query, allow-recursion or allow-cache statements in
> your other config files.
Did this. The o
These two views are identical in any way I can see, so the fault may be
in an included configuration file that is not included in your message.
Look for allow-query, allow-recursion or allow-cache statements in your
other config files.
When using views, I often find it more manageable to move
Hi!
I have set up a view for one site. It is bound to change answers as
necessary for different IP-ranges. It works as far as I could see.
But with one ip-range there is a problem ...
I can query internal addresses:
!user@kvm2~# host intweb.example.de
!web.example.de has address 192.168.180.46
B
On 6/18/2011 12:08 AM, Thomas Schweikle wrote:
Hi!
I have set up a view for one site. It is bound to change answers as
necessary for different IP-ranges. It works as far as I could see.
But with one ip-range there is a problem ...
I can query internal addresses:
!user@kvm2~# host intweb.example
Hi!
I have set up a view for one site. It is bound to change answers as
necessary for different IP-ranges. It works as far as I could see.
But with one ip-range there is a problem ...
I can query internal addresses:
!user@kvm2~# host intweb.example.de
!intweb.example.de has address 192.168.180.46
6 matches
Mail list logo
