My IXFR/AXFR stopped suddenly

[Blason R]

Well, I just tried transferring zone using dig and it was successful from
slave

On slave
dig AXFR block.now @xx.xx.xx.xx

On master xfer-out.log

07-Jul-2018 09:53:11.520 client xx.xx.xx.xx#16129 (immediate.block):
transfer of 'block.now/IN': AXFR started (serial 2018061016)
07-Jul-2018 09:53:11.521 client xx.xx.xx.xx#16129 (immediate.block):
transfer of 'block.now/IN': AXFR ended



On Sat, Jul 7, 2018 at 9:07 AM Blason R <blason16 at gmail.com> wrote:

> Yes Anand is right; I didnt diclose the full config at Slave but its been
> configured to listen on port 15455 and that UDP port is listening and I can
> connect to that port using nc.
>
> It was in fact working absolutely fine but suddenly it stopped.
>
> @Ananad - can you confirm what command should I run on slave to debug and
> that is what I wanted which I am not aware of.
>
> On Sat, Jul 7, 2018 at 3:28 AM Anand Buddhdev <anandb at ripe.net> wrote:
>
>> On 06/07/2018 23:52, Sten Carlsen wrote:
>>
>> Hello Sten,
>>
>> >> The slave is configured to listen on port 15455.
>> > Where in the slave's configuration is that specified? Rather the master
>> > sends notifys on two ports: 53 and 15455.
>>
>> Blason has not shown his full config, but it must be listening on port
>> 15455 to be receiving the NOTIFY message, as shown by the log entry.
>>
>> The master has:
>>
>> notify explicit;
>> also-notify {
>>     2.2.2.2 port 15455;
>> };
>>
>> This tells the master to notify 2.2.2.2 on port 15455. There is no
>> notify on port 53. What made you think that port 53 is being used?
>>
>> Anand
>> _______________________________________________
>> 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/20180707/f8aacdcb/attachment.html>