My IXFR/AXFR stopped suddenly
Matus UHLAR - fantomas
uhlar at fantomas.sk
Fri Jul 6 17:36:54 UTC 2018
>On 06/07/2018 15.46, Blason R wrote:
>> Any clue how do I troubleshoot why master to Slave IXFR/AXFR stopped?
>> It was working before even my logs shows notifies..I can connect to my
>> slave on customised port that NOTIFY messages are sent but then PULL
>> from slave to master is not working.
customised port, that's why transfers stopped working.
>> Master
>> zone "block.now" {
>> type master;
>> file "/var/lib/bind/zones/block.now.db";
>> notify explicit;
>> also-notify {
>> 2.2.2.2 port 15455;
>> };
>> allow-transfer {
>> 2.2.2.2;
>> };
>>
>>
>> ON SLAVE
>> zone "block.now" {
>> type slave;
>> file "/var/lib/bind/zones/block.now.db";
>> masters { x.x.x.x; };
>> allow-transfer { none; };
>> allow-query { localhost;};
>> allow-notify { x.x.x.x; };
>> };
On 06.07.18 19:28, Sten Carlsen wrote:
>Maybe I am missing something but how will the slave know that it must
>use port 15455?
on the slave, you must configure the master with port 15455.
see "server" directive.
of course, it will use port 15455 for all queries then.
>> 06-Jul-2018 14:10:28.341 client x.x.x.x#10090: received notify for
--
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.
Christian Science Programming: "Let God Debug It!".
More information about the bind-users
mailing list