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 is
Sounds good. I will just buckle down and stay the course. As I encounter these
servers, I have been attempting to reach out to all of the organizations whose
DNS servers exhibit this behavior. Some are less responsive than others, as in
completely ignored. :/
Thanks for the feedback.
_
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.
1)
Hi.
It was not oracle linux 9.16 but Bind 9.16.
The problem seemed to be about broken dnssec validation, that's why commenting
those entries solved.
For now I'm not using dnssec, I will have to read about key rotation. If that
is still a very manual process, I'll have to be quite confident before
5 matches
Mail list logo
