Navigate to in your browser and follow the wizard.I will not go in to all configuration here but some things are needed to make this work optimal with OPNsense. Now we are ready to configure AdGuard Home itself. Check Register DHCP leases and Register DHCP static mappings, this will resolve hostnames for us in AdGuard Home.Navigate to Services: Unbound DNS: General.We need to change this so they don't conflict with each other. Out of the box OPNsense is already running Unbound on this port. Since DNS as default is listening on port 53 we also want AdGuard Home to listen on this port to make or life easier.

Go to Services: Adguardhome: General and enable the plugin, then save.Head over to System: Firmware: Plugins and search for AdGuard and install it.

Reverse the steps above to disable SSH again. Now connect to OPNsense over ssh and run this command fetch -o /usr/local/etc/pkg/repos/nf

In OPNsense WebUI, navigate to System: Settings: Administration.

If you already have set up SSH you can ignore this. If you don't need to have ssh activated all the time (especially not for root) we can temporarily activate it just for this occasion. Make AdGuard Home installable as a pluginįirst we need to add mimugmail community repo, so we can install AdGuard Home as a plugin. So let's install AdGuard Home on the same device as OPNsense.

With this new router I think it's a good idea to combine router and DNS since they should work together as much as possible. One of the most important services I host is AdGuard Home, which I've been running on either a dedicated Raspberry Pi or in Proxmox. A small, dedicated hardware running OPNsense. Since going the self-hosted and open-source path recently, the choice was easy. I recently decided to upgrade my old Asus router to something more modern and fun.

Adguard cnameclaburn