DNAME not applied more than once to resolve the query
SivaKesava1 opened this issue · comments
Siva Kesava R Kakarla commented
Same issue as in Knot: https://gitlab.nic.cz/knot/knot-dns/-/issues/714
Wouter Wijngaards commented
It is a feature, not a bug. The reason is that it is seen as a DNAME loop, because the same DNAME is applied twice. If it was two different DNAMEs then there would be two DNAMEs in the answer.
Wouter Wijngaards commented
But fixed it anyway, because the same behaviour as BIND is desirable. The fix tests if the CNAME can be added. That results in the NS record returned in the example you gave. Thanks for the report!