Job wrote:
>
> is there a way to define more response-policy in Bind or the possibility
> to apply a response-policy only to certain client ip?
There is the RPZ-CLIENT-IP trigger, which applies to any query from a
matching client IP address. Or you can use views to apply different RPZ
policies to
>>That's how passthru is supposed to work.
Hi Tony,
is there a way to define more response-policy in Bind or the possibility to
apply a response-policy only to certain client ip?
Thank you again!
Francesco
Tony.
--
f.anthony.n.finchhttp://dotat.at/ - I xn--zr8h punycode
Wight, Portland
Job wrote:
>
> i add that, if i have a pass-throu define in second zone
> (rpz-dyndns.lan), the third RPZ zone is NOT applied.
>
> If i have no pass-through in the previous definition, it works!
That's how passthru is supposed to work.
Tony.
--
f.anthony.n.finchhttp://dotat.at/ - I xn--zr
>colostate.edu. 172800 IN NS dns1.colostate.edu.
>colostate.edu. 172800 IN NS dns3.colostate.edu.
>;; Received 119 bytes from 192.41.162.30#53(l.edu-servers.net) in 78 ms
>
>www.cloudsat.cira.colostate.edu. 3600 IN CNAME dpc.cira.colostate.edu.
>dpc.cira.co
In article ,
Matus UHLAR - fantomas wrote:
> On 18.05.16 14:10, Con Wieland wrote:
> >I am having an issue resolving www.cloudsat.cira.colostate.edu from 2 of my
> > name servers. I have 2 others with identical configs that resolve
> > correctly. A normal lookup shows a server fail but a +trac
On 18/05/16 22:10, Con Wieland wrote:
I am having an issue resolving www.cloudsat.cira.colostate.edu
"rndc dumpdb" can be helpful in this case, IME. Dump the cache then
inspect the records and parent delegations, see what bind thinks is
in-cache when it's broken.
On 18.05.16 14:10, Con Wieland wrote:
I am having an issue resolving www.cloudsat.cira.colostate.edu from 2 of my
name servers. I have 2 others with identical configs that resolve
correctly. A normal lookup shows a server fail but a +trace looks ok.
Any ideas how to better troubleshoot the iss
Hello,
i add that, if i have a pass-throu define in second zone (rpz-dyndns.lan), the
third RPZ zone is NOT applied.
If i have no pass-through in the previous definition, it works!
Thank you,
Francesco
Da: bind-users-boun...@lists.isc.org [bind-users-bou
Hello,
within in a view i have added the third rpz zone (i take it separately), it is
loaded but the RPZ policy does not act.
If i leave only two zones, it works perfectly.
Is there a limit of two zone consequentially?
How can i avoid it?
Here is my configuration:
response-policy { zone "rpz.l
9 matches
Mail list logo