- #ADGUARD HOME INSTALL#
- #ADGUARD HOME UPGRADE#
Under OPNsense you can navigate to System: Settings: General and add backup DNS servers under Networking -> DNS servers, but if you leave them empty only AdGuard Home will be used. You should, of course, tweak the other settings and add some filter rules, but that is standard AdGuard Home configuration. That's the only settings you need to do to make this work.
Now you will resolve local machines when connected to your LAN, and if connecting over the internet the public DNS record will be used instead. In AdGuard Home navigate to Settings -> DNS settings and go to top section under Upstream DNS servers. Let's say you've entered a domain under System: Settings: General that is, and you want that to take precedence over the public DNS, if that also exists, when you are at home. If you use a domain name to resolve local hosts by name instead of IP you might need to tweak that in AdGuard Home as well. Here we enter the Unbound server we changed earlier in OPNsense settings, 192.168.1.1:5353, or with other port pointing to you OPNsense instance if you have another one. In AdGuard Home navigate to Settings -> DNS settings and scroll down to Upstream DNS servers -> Private reverse DNS servers. When the wizard is complete we can login to AdGuard Home with the credentials you entered. In the next step pick a username and password. The DNS Server can listen on all interface and use the default port 53. Set the Admin interface to listen on your router IP only (often 192.168.1.1), the same you use when configuring OPNsense itself. 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. #ADGUARD HOME INSTALL#
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.
#ADGUARD HOME UPGRADE#
I recently decided to upgrade my old Asus router to something more modern and fun.
0 kommentar(er)
