SomeWhereOverTheRainBow
Part of the Furniture
This issue has been resolved already. It was a problem with Adguardhome not properly reading the dnssec data from Unbound once DNSSEC was enabled inside AdGuardHome (to be a bit more specific, the EDE data). DNSMASQ, and Pihole consequently had this same issue as well. Overall, it has been resolved across the board.Old thread - but I recently changed to DietPI on my RPI4 and installed Unbound along with AGH, and now DNSSEC works and passes all tests:
View attachment 51428
Not sure if this is related to the version of Unbound being updated due to now running Debian Bookworm - I know the previous version available in Debian Bullseye was a couple of versions behind.
I don’t think it was anything in my Unbound conf file as I copied that over as well…

Dig through SERVFAILs with EDE
Now we’re happy to announce we will return more error code types and include additional helpful information to further improve your debugging experience.

Last edited: