derKief

@Chinaski1 @ameshkov Are there any parallels with my problem? It certainly reads very similar. [DNSSEC issue with OpenWRT/Unbound and paid Adguard DNS](https://github.com/AdguardTeam/AdGuardDNS/issues/809)

updating to OpenWrt 23.05.4 - Service Release doesn't help. At the moment the only option is to either disable DNSSEC or use Adguard free DNS

I found this in Unbound changelog https://github.com/NLnetLabs/unbound/blob/master/doc/Changelog **25 July 2024: Wouter - Add root key 38696 from 2024 for DNSSEC validation. It is added to the default root keys in...

@Chinaski1 any news on this?

meanwhile i tried DoT with Stubby+DNSmasq on OpenWRT. Same issue. As soon as i activate DNSSEC i get this issue. Unfortunately the logs doesn't really help. I running out of...

@Chinaski1 over at Openwrt forum they mentioned that the problem may be related to alternative dnssec root key you are implementing. The problem is annoying now because nobody can or...

I'm following the instructions on my Dashboard at https://adguard-dns.io/ I cannot test your link because DoT isnt working with private DNS settings Only free public DNS are working. *Configure DNS-over-TLS...

still not working. Every party says its not our fault ... we didnt change anything. I also have issues with Adgaurd on my mobile and Adguard support is also not...

Since no one has been able to help me so far, I have switched to dnsproxy.

As dnsproxy is not really reliable on OpenWRT for me i switched back to old confugartion. This time i tried stubby but still same issue. Followed the guide here ->https://openwrt.org/docs/guide-user/services/dns/dot_dnsmasq_stubby...