![]() It could well be user error, but it feels like AdGuard is running on my router hardware but is not really integrated with the rest of the functions of the router. It doesn't seem like AdGuard is resolving the local client names either. I'm not sure what the best configuration is. It looks like you can either disable unbound or set unbound to forward to AdGuard. I installed it and have started configuring it on my router. I noticed that OPNsense now has an AdGuard Home plugin. Plus, who wants to use two devices when one will do? Anyway I was hoping for a more integrated solution. I considered doing DHCP on my PiHole as well, but then I would need to look up names when examining logs on OPNsense. For example, I have a static IP and friendly name assigned to every device on my network so it's really easy to look examine network traffic, but I have to keep updating the DNS list on the PiHole to match changes I have made in the router. It's certainly easy to use but I would prefer to have my DNS built in to the rest of my router. I have been using a PiHole on a separate device as my DNS for some time, first in forwarding mode and then in recursive mode. I'm primarily interested in the method that results in the lowest latency, but ease of use is also good-nice graphs, client-by-client filter rules, ease of adding to whitelists/blacklists etc. I'm having a hard time sorting through them to know which is the best practice and what the advantages/disadvantages of each are. There are multiple solutions for DNS ad filtering when using OPNsense, and multiple ways of configuring those solutions-three big ones that I have seen.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |