Running the latest Adguard on OPNsense 25.7.10-amd64, Protectli VP2430
Clean install of OPNsense. Added the community plug-in for Adguard, configured with Unbound as per the how-to here (https://windgate.net/setup-adguard-home-opnsense-adblocker/). Updated to the latest Adguard via the Adguard admin page.
Ran fine for a few weeks, then one night it just stopped responding to DNS requests from clients on my network. I tried re-booting, then finally disabled it altogether and moved Unbound back to port 53.
I'd really like to get it working again. Any suggestions where I should look?
AGH logs? Test with dig/drill/nslookup on the command line.
Quote from: hooter on January 07, 2026, 09:24:43 PMI'd really like to get it working again. Any suggestions where I should look?
My AGH -> Unbound setup runs fine (and has run fine) for several years, so it is something in your setup.
As one data point: Do not use port 5353. That port is used for mDNS. Most of the guides get this wrong because 5353 is just so convenient and easy to remember ...
That probably does not explain your issues, though.