EDE 18/20 recursion failures after devel release upgrade 9.21.14 -> 9.21.15. bug, or config change req'd?

[Greg Choules]

I think it might also be useful to enable querylog and answerlog to have
positive confirmation of which view the server used to attempt to handle
the query. A pcap as well would be icing on top :)

Cheers, Greg

On Wed, 19 Nov 2025 at 14:39, Colin Vidal <colin at isc.org> wrote:

> On Wed, 2025-11-19 at 09:31 -0500, pgnd wrote:
> > > Looking at the dig flags it suggests you changed your config.
> >
> > _my_ config is untouched.
> >
> > drop back to v9.21.14, all's good again.
> >
> > > 9.21.15 introduces a new rndc command `showconf -effective`. The
> > > output of this command would be useful.
> >
> > reproduced on a couple of server instances.
> > also, with different/older dig client versions.
> > in all cases, v9.21.14 and prior, good.
> >
> > on my local dev box,
> >
> > $ rndc showconf -effective
> >       ...
> >
> > WAY too noisy/verbose for my taste, so redacted ... hth
> >
> > $ rndc showconf -effective
>
> Thank you. Looking at the query I assume the view "internal" was used,
> and recursion seems enabled/allowed indeed. Could it be possible to
> also provide the named.conf? (external and chaos views are not needed)
> I'll attempt to reproduce.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20251119/18ea1028/attachment.htm>