OK - It seems there is a lot of confusion on setup as I didnt give the
entire config.
Here is my entire config
*Master config*
zone "block.now" {
type master;
file "/var/lib/bind/zones/block.now.db";
notify explicit;
also-notify {
2.2.2.2 port 15455;
On 07.07.18 11:31, Blason R wrote:
Well after numerous try I could not succeed hence then I had to delete the
block.now.db file and had to restart the service
it then done the AXFR and later IXFR started as well.
have you incremented the serial number on master?
if the serial on the slave is b
On 07/07/2018 13:31, Alan Clegg wrote:
>> 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 'blo
On 7/7/18 12:25 AM, Blason R wrote:
> 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':
Well after numerous try I could not succeed hence then I had to delete the
block.now.db file and had to restart the service
it then done the AXFR and later IXFR started as well.
On Sat, Jul 7, 2018 at 9:55 AM Blason R wrote:
> Well, I just tried transferring zone using dig and it was successful
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.5
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 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
15
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
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 t
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
Hi
On 06/07/2018 15.46, Blason R wrote:
> Hi Team,
>
> 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
Hi Team,
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.
Master
zone "block.now" {
type ma
13 matches
Mail list logo
