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

[pgnd]

> 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.

1st, minor confusion here.  not clear on the point you're making, or what you're looking for.

it's a lookup of a NON-local domain, that's NOT one of my zones. specifically

	dig A isc.org @::1

here, with

	$ cat named.conf*

		...
		view "external" {
			match-clients {
				!key internal-rndc-key ;
				key external-rndc-key ;
				...
			};
		...
		view "internal" {
			match-clients {
				!key external-rndc-key ;
				key internal-rndc-key;
				localhost;
				...
			};
		...

it shouldn't matter (?)

	$ named -v
		BIND 9.21.14 (Development Release) <id:noscm>
	$ dig A isc.org @::1 -k ./internal.rndc.key +short
		151.101.2.217
		151.101.66.217
		151.101.130.217
		151.101.194.217
	$ dig A isc.org @::1 -k ./external.rndc.key +short
		151.101.66.217
		151.101.130.217
		151.101.194.217
		151.101.2.217

	$ named -v
		BIND 9.21.15 (Development Release) <id:noscm>
	$ dig A isc.org @::1 -k ./internal.rndc.key +short
	$ dig A isc.org @::1 -k ./external.rndc.key +short

whereas for one of _my_ split-horizon zones, (e.g.)

	$ dig MX example.com @::1 -k ./internal.rndc.key +short
		5 mx.example.net.
	$ dig MX example.com @::1 -k ./external.rndc.key +short
		5 mx1.example.com.
		10 mx2.example.com.