My IXFR/AXFR stopped suddenly

[Sten Carlsen]

On 06-07-2018 23.49, Anand Buddhdev wrote:
> On 06/07/2018 19:36, Matus UHLAR - fantomas wrote:
>
>> customised port, that's why transfers stopped working.
> No Matus, you're wrong.
>
>> 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.
> No, you're off the track here.
>
> Blason's config means this:
>
> 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.
>  The master has been
> told to send a NOTIFY to the slave. The master will originate this
> NOTIFY message from a random source port, and send it to the slave on
> destination port 15455.
>
> The slave is obviously receiving the NOTIFY message, as evidence by the
> log message on the slave:
>
> 06-Jul-2018 14:10:28.341 client x.x.x.x#10090: received notify for zone
> 'block.now'
>
> At this point, the slave should refresh the zone from the master. Blason
> says it's not refreshing.
>
> Blason, try debugging by using "dig" on the slave to manually transfer
> the zone from the master. Maybe that will give you a clue to the problem.
>
> 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

-- 
Best regards

Sten Carlsen

No improvements come from shouting:

"MALE BOVINE MANURE!!!"