Running a network-wide ad blocker can silence intrusive ads on every gadget in your home, from smartphones to smart-light controllers. AdGuard Home provides exactly that by acting as a DNS server that refuses requests to known advertising, tracking, and malicious domains. When paired with a ZimaOS box, the solution lives on hardware you already control, eliminating the need for third-party services.
This walkthrough assumes a functional ZimaOS installation and a willingness to adjust a few network settings. You will learn how to allocate the required ports, install the Docker-based AdGuard Home container from the ZimaOS App Catalog, configure static addressing, and finally point your router’s DNS to the new service. Optional blocklist expansion is also covered.
1. Preparing the ZimaOS Device and Reserving Ports
Before pulling the application, verify that ports 82 and 3001 are free on the host. ZimaOS maps these host ports to AdGuard Home’s internal ports 80 (web UI) and 3000 (setup wizard). Additionally, port 53 must remain unoccupied because it carries DNS traffic. If any of these ports clash with existing services, choose an alternative host port and remember to substitute it in every subsequent reference.
Next, open the ZimaOS App Store, search for “AdGuard Home,” and click **Install**. The package is a pre-configured Docker container, so no manual image handling is required. Once the download finishes, head to the app’s settings page and add a port-forwarding rule that maps host port 82 to container port 80. The interface provides a ‘+’ button for this purpose. Should the system reject the rule, it indicates that port 82 is already taken; pick another free host port and adjust the rule accordingly.
2. Running the Initial Setup Wizard
Launch AdGuard Home from the ZimaOS dashboard. The first-time wizard appears on port 82 (or the alternative you selected). Stick with the default values, which already enable the built-in AdGuard DNS filter. Create an administrator username and a strong password when prompted. By default, the admin panel listens on every network interface, which is convenient for home use but may need tightening for security-conscious environments; consult the official AdGuard documentation for hardened configurations.
After the wizard finishes, return to the app’s configuration screen. In the Web URL field, replace the displayed 3001 with the host port you mapped earlier (typically 82). Save the changes, then reopen the AdGuard Home icon and log in using the credentials you just set. You should now see the dashboard, where query logs and blocking statistics begin to populate in real time.
3. Assigning a Static IP and Redirecting Router DNS
To keep the DNS service reachable, give the ZimaOS box a permanent address. Open ZimaOS Settings → Network, select the active interface, and switch the addressing mode from “Automatic (DHCP)” to “Manual.” Fill in values that match your local subnet, for example:
- IP address: 10.0.1.91
- Subnet mask: 255.255.255.0 (or /24)
- Gateway: 10.0.1.1
- DNS: 94.140.14.14 (primary) and 94.140.15.15 (secondary)
Save the configuration. If you prefer not to set a static address directly, you can reserve the same IP on your router’s DHCP lease table, ensuring the device always receives the same address after a reboot.
Finally, access your router’s administration panel, locate the DHCP/DNS settings, and replace the default DNS server with the static IP you just assigned (e.g., 10.0.1.91). Apply the changes and restart the router if necessary. All devices that obtain their network configuration via DHCP will now query AdGuard Home for DNS resolution, automatically benefiting from ad and tracker blocking.
Optional: Enriching the Blocklist Collection
AdGuard Home ships with a reputable default filter, but you can widen protection by adding extra lists. In the dashboard, navigate to Filters → DNS blocklists → Add blocklist. Paste the URL of any publicly maintained list—such as those targeting ransomware, adult content, or regional ad networks—and confirm. Each added source augments the domain-level blocking that applies to every client on the LAN.
Remember that DNS-based filters cannot suppress ads embedded on the same domain as the content you are viewing, like YouTube video ads or most in-app advertisements. Those require a dedicated client-side blocker.
Whenever a newer AdGuard Home version appears in the ZimaOS App Store, reinstall the updated package to stay current. Docker containers do not self-update, so the built-in “Update” button inside the UI will remain inactive.
If you encounter difficulties, the ZimaSpace Discord community offers real-time assistance from both staff and experienced users.
