On 12/11/22 4:43 PM, Duncan Findlay wrote:
I tried reproducing this issue with several modified versions of aardvark-dns to see if I could narrow down the cause. I could not reproduce this with upstream source at head, nor with upstream source at v1.0.3.
Thanks for your test report. I'm currently updating trust-dns to version 0.22, and am hopeful that this will resolve the issue. In fact, trust-dns in version 0.21 had to disable quite some features that I didn't think would impact how aardvark-dns was using it. Maybe I was wrong, in which case the upgrade would help. -rt
