I'm having issues with unbound resolving DNS. It happens with popular destinations such as github.com and reddit.com. I used to run pfsense before moving to opnsense with the same setup and never experience this issue. I've had this issue using Dnsmasq and recently with Kea.
My setup is as follows. My LAN uses Adgurad home, which is on a Raspberry Pi. Now using Kea, the LAN DNS is set to Adguard. Adguard's DNS is set to Unbound. The LAN points to 10.10.60.190 and the Adguard points to 10.10.60.1:53. It's fairly straightforward.
Unbound is setup on port 53. DNSSEC and Flush DNS Cache during reload are enabled.
Could this be an issue with unbound receiving requests from Adguard?
I dunno, I use 9.9.9.11 for all my dns, set by DHCP from fw. Point your Adguard to 9.9.9.11. Done.
For now, I'm testing without Adguard to see if there are issues. If none, I'll point to upstream DNS in Adguard. I like having unbound be a DNS resolver.
There is definitely an issue with Unbound. I'm getting the block again for sites I can access on my carrier network. This is with Unbound getting requrest directly and Adguard out of the picture.
Now I will enable Adguard and use upstream DNS servers.
Didnt mention if your running IPS
Didnt mention dns server setup
Finally mentioned it was a block
Didnt mention if browser is setup