Mea Culpa. Apparently RPZ IS the issue here.
I learn something new every time I read this list.
My apologies for the waste of bandwidth.
Bob
On Mon, Jan 16, 2023 at 9:02 AM Bob McDonald wrote:
> This is just conjecture but I'll take a stab at this problem.
>
> First, the fact that the zone
On 16. 01. 23 15:02, Bob McDonald wrote:
This is just conjecture but I'll take a stab at this problem.
First, the fact that the zone is RPZ really doesn't have any bearing on
this problem.
Well, that's incorrect. Please see
https://lists.isc.org/pipermail/bind-users/2023-January/107212.html
This is just conjecture but I'll take a stab at this problem.
First, the fact that the zone is RPZ really doesn't have any bearing on
this problem.
Do you control both the primary and secondary zones?
Please provide the SOA for the zone. This will allow the list to see some
key timer values.
On 15. 01. 23 19:02, Jesus Cea wrote:
I have a huge zone receiving a constant flow of small dns updates. My
secondaries receive notifications and transfer the zone incrementally.
Cool, everything works as expected.
Nevertheless, I see this lines in my logs, constantly (every time a
change
On Sun, 15 Jan 2023, Jesus Cea wrote:
I have a huge zone receiving a constant flow of small dns updates. My
secondaries receive notifications and transfer the zone incrementally. Cool,
everything works as expected.
[...]
Ok, my updates are coming too fast (first line). No problem, the
I have a huge zone receiving a constant flow of small dns updates. My
secondaries receive notifications and transfer the zone incrementally.
Cool, everything works as expected.
Nevertheless, I see this lines in my logs, constantly (every time a
change arrives incrementally):
"""
15-Jan-2023
6 matches
Mail list logo