You did not report back the results of the other 2 troubleshoot actions
that Brian suggested (dig and tcpdump)
These could hold clues to the cause of your problem.
On Tue, 2022-12-06 at 14:33 -0500, Curtis Maurand via Pdns-users wrote:
> OK, just did the upgrade and adjusted the tables accordingly
I do not, but I will try to get the message back, the reverse way this
problem reached me :)
I sure hope they do not have old F5's, though. Security wise I mean.
On Fri, 2022-10-07 at 13:58 +0200, Peter van Dijk via Pdns-users wrote:
> On Thu, 2022-09-22 at 09:27 +0200, Leeflangetje
It is recommended to inform the owner of the zone in
> > > order to fix the root cause.
> > >
> > > Winfried
> > >
> >
> > Agreed, but given my findings in the other post I'm not convinced
> > it
> > will solve *all* issues
Hi,
Since we upgraded to pdns-recursor 4.6 we sometimes experience some
weird behaviour with queries via pdns-recursor.
Sometimes, when a previously queried record expires through it's TTL,
the recursor does not provide an answer anymore, until it's restarted.
Unfortunately I am not able to repr
Hi :)
I have a setup with pretty old pdns servers (4.2).
One hidden master that serves a number of internet-facing authorative
servers which act as superslaves.
I want to upgrade the lot to the latest version, but preferably without
any downtime.
One way to do that (hopefuly) is to upgrade each
