also-notify and allow-notify

[Blason R]

Nah that is not my query; instead I wanted updates to be sent on other
port  and not TCP/53. Queries let it happen on UDP 53

On Fri, May 18, 2018 at 3:02 PM, Matus UHLAR - fantomas <uhlar at fantomas.sk>
wrote:

> On 17.05.18 23:00, Blason R wrote:
>
>> I have RPZ installed on server and its acting as a master server but
>> somehow port setting is not working on master
>>
>
> ######### Slave configuration
>>
>> response-policy { zone "malware.trap"; };
>>
>> zone "malware.trap" {
>>  type slave;
>>  masters { 192.168.5.48; };
>>   file "/var/lib/bind/malware.trap.db";
>>  allow-notify { 192.168.5.48; };
>>
>
> this is superflous. The default is to accept notifies from master.
>
>  allow-query {localhost; };
>> };
>>
>>
>> So here I am sending notification  to 192.168.5.49 on port 4545; my
>> queries
>> are
>>
>
>   1. How do I configure port on slave 4545 so that slave server can start
>>   listening on that port.
>>
>
> why do you need to listen on port 4545 instead of default 53?
>
> --
> Matus UHLAR - fantomas, uhlar at fantomas.sk ; http://www.fantomas.sk/
> Warning: I wish NOT to receive e-mail advertising to this address.
> Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
> We are but packets in the Internet of life (userfriendly.org)
>
> _______________________________________________
> Please visit https://lists.isc.org/mailman/listinfo/bind-users to
> unsubscribe from this list
>
> bind-users mailing list
> bind-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20180518/0675c4e0/attachment.html>