Hello,

I am attempting to migrate some internal bind servers to knot+knot-resolver. We have knot acting as the authoritative server for internal views of our public zones and we're attempting to use Knot Resolver to forward to Knot to provide recursive resolution on the internal network.

In this configuration, when Knot is resolving a CNAME record from an internal stub zone, it doesn't chase the target of the CNAME for the client.

To demonstrate, here are two example zones served by knot:

# zone1.com

test-a 30 IN A 192.168.1.1

# zone2.com

test-cname 30 CNAME test-a.zone1.com.

With these configured as stubs in Knot Resolver, if you query test-cname.zone2.com, knot resolver won't chase it across zones to get the A record value like it would for non-stub zones.

Both Bind9 and Unbound chase this as expected. Is there any way to configure Knot Resolver to do the same?

Thanks!

- Paul