Re: My IXFR/AXFR stopped suddenly
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 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 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 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
Re: My IXFR/AXFR stopped suddenly
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 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 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
Re: My IXFR/AXFR stopped suddenly
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 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
Re: My IXFR/AXFR stopped suddenly
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
Re: My IXFR/AXFR stopped suddenly
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@lists.isc.org > https://lists.isc.org/mailman/listinfo/bind-users -- Best regards Sten Carlsen No improvements come from shouting: "MALE BOVINE MANURE!!!" ___ 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
Re: My IXFR/AXFR stopped suddenly
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. 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@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: My IXFR/AXFR stopped suddenly
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, uh...@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!".
___
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
Re: My IXFR/AXFR stopped suddenly
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 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; };
> };
>
Maybe I am missing something but how will the slave know that it must
use port 15455?
> 06-Jul-2018 14:10:28.341 client x.x.x.x#10090: received notify for
> zone 'block.now'
> 06-Jul-2018 14:14:54.988 client x.x.x.x#10093: received notify for
> zone 'block.now'
>
>
>
>
>
> ___
> 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
pEpkey.asc
Description: application/pgp-keys
___
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
My IXFR/AXFR stopped suddenly
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 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; };
};
06-Jul-2018 14:10:28.341 client x.x.x.x#10090: received notify for zone
'block.now'
06-Jul-2018 14:14:54.988 client x.x.x.x#10093: received notify for zone
'block.now'
___
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
Re: round-robin bug in 9.12.1-P2 for rDNS?
> > This sounds a bit like #336 [1], > > Nope - we got bit by that when we upgraded > to 9.12, which is what resulted in the explicit > config for rrset-order. > > > If you can still reproduce this with current > > master (or with current v9_12 branch), please > > open a new GitLab issue. > > Please forgive my ignorance on this point, > but is running the FreeBSD package for > 9.12.1-P2 sufficient to meet this? It probably is, the #336 bit above was a long shot. Please open a GitLab issue, supplying version information and a configuration which allows reproducing this behavior. Thanks! -- Best regards, Michał Kępień ___ 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
