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 <ana...@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@lists.isc.org > https://lists.isc.org/mailman/listinfo/bind-users >
_______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users