AdGuard Home must parse and rebuild filtering state. Upstream issue history and current user reports show large filter sets can create noticeable transient pressure on small devices.
Users with many large blocklists.Hardwareanforderungen für AdGuard Home: RAM, DNS-Cache und Filter
Erfahre mehr über die Anforderungen von AdGuard Home an RAM, DNS-Cache, Filter, Abfrageprotokoll und verschlüsseltes DNS und wähle anschließend passende ZimaOS-Hardware aus.
AdGuard Home requirements at a glance
AdGuard Home upstream does not publish one universal CPU or RAM minimum. The core DNS service is lightweight enough to run on routers and small servers, but memory and CPU use can rise with large filter lists, cache size, query logging, Safe Browsing/Safe Search features, encrypted DNS and many clients. OpenWrt's current AdGuard Home guide gives 50 MB free RAM and 100 MB free storage as general platform guidance, not an upstream AdGuard requirement.
- CPU
- No numerical upstream minimum. Query rate, encrypted DNS and filter updates determine heavier CPU demand.
- RAM
- No numerical upstream minimum. Large filters, DNS cache, query logs and auxiliary protection caches can increase memory.
- OpenWrt guidance
- 50 MB free RAM and 100 MB free storage are current OpenWrt general guidance only—not AdGuard Home's official universal minimum.
- DNS cache
- AdGuard Home exposes DNS cache size in bytes, so memory usage can be deliberately bounded/tuned.
- Query log
- Query logging and statistics add memory/disk activity. Long retention or busy networks can create more write and memory overhead.
- Best Zima starting point
- ZimaBoard 2 832 is vast overkill for AdGuard Home alone and is ideal when DNS filtering shares the host with other network/home-server services.
From official requirements to the right setup
AdGuard Home sizing starts with DNS traffic and filter complexity, not a fixed device-count rule.
-
Official requirements
Count clients and approximate DNS query rate. A small home network is very light; busy multi-user networks, IoT fleets and encrypted DNS endpoints create more work.
-
Confirm your needs
Review filter-list size and cache settings. AdGuard Home stores DNS cache in memory and parses filter rules, so very large lists can change memory behavior.
-
Leave room to grow
Plan query-log/statistics retention and disk placement. Logs and periodic filter updates can create writes that are more noticeable on small flash devices than on a normal ZimaOS server.
-
Run it on ZimaOS
Install AdGuard Home from ZimaOS, monitor query latency, process memory and filter-update peaks, then tune lists/cache/logging before adding hardware.
Check every playback client
- Number of DNS clients
- Queries per second
- Filter list count and rule volume
- DNS cache size
- Query-log retention
- Safe Browsing / Safe Search features
- DoH/DoT/DoQ use
- Primary/secondary DNS availability
Official minimum requirements
AdGuard Home's upstream documentation does not publish a universal host CPU/RAM minimum.
Keep upstream requirements separate from platform guidance. The 50 MB RAM / 100 MB storage figures sometimes quoted online come from OpenWrt's deployment guide, not a universal AdGuard Home minimum.
| Requirement | Official minimum | What this supports |
|---|---|---|
| CPU | No numerical upstream minimum | Workload depends on DNS traffic, encryption and filters. |
| RAM | No numerical upstream minimum | Caches, filters and logs are the main variable consumers. |
| OpenWrt general RAM guidance | 50 MB free RAM | Platform guidance only; not an AdGuard upstream minimum. |
| OpenWrt general storage guidance | 100 MB free storage | Platform guidance only; logs/filter data can require more. |
| DNS cache | Configurable in bytes | Current AdGuard Home configuration exposes cache_size. |
| GPU | Not required | DNS filtering and encrypted DNS are CPU/network workloads. |
When to upgrade your hardware
Upgrade only when the DNS/filter workload or whole networking stack shows real pressure.
Large filter updates cause memory or CPU spikes
Encrypted DNS and high query rates raise CPU use
AdGuard Home shares the host with VPN/proxy/network services
DoH/DoT/DoQ adds cryptographic/protocol overhead compared with plain LAN DNS, especially when many clients use the host directly.
Busy networks or public/encrypted DNS deployments.WireGuard, reverse proxies, tunnels and monitoring can dominate the combined server workload even when DNS filtering remains light.
All-in-one network appliances.Plan hardware growth with confidence
Scale AdGuard Home by tuning filters, caches and resilience before buying more compute.
Use only useful filter lists
More lists are not automatically better; larger rule sets increase parse/update work and can consume more memory.
Reduce redundant lists before treating a filter-update spike as a hardware problem.Tune DNS cache deliberately
AdGuard Home lets you configure cache_size in bytes, giving direct control over one memory consumer.
Increase only when cache behavior and RAM headroom justify it.Limit query-log/statistics retention if disk writes matter
Busy DNS servers can produce significant query-log/statistics churn over time.
Useful for flash-constrained devices; ZimaOS SSD/eMMC has far more headroom.Add a second DNS resolver for resilience
A larger single server does not prevent DNS outage during host maintenance or failure.
Redundancy can be more valuable than a faster primary DNS server.Can it run on ZimaOS?
AdGuard Home is currently available in the ZimaOS App Store under Networking.
Install AdGuard Home from the ZimaOS App Store
Use the packaged network-wide DNS filtering service and persist its configuration/data.
Open AdGuard Home in the ZimaOS App StoreTune cache and filters from current upstream configuration
AdGuard Home's configuration reference exposes cache, filtering, Safe Search and query-log settings that directly affect resource use.
Read AdGuard Home configurationDo not confuse platform guidance with upstream minimums
OpenWrt provides useful small-router guidance, but it should remain labelled as platform-specific rather than an AdGuard universal requirement.
Read OpenWrt AdGuard Home guidanceChoose Zima hardware for AdGuard Home
AdGuard Home is far too lightweight to justify high-end hardware on its own. Pick the Zima tier for the other networking and server workloads around it.
Is AdGuard Home a standalone DNS filter or part of a larger network server?
Home DNS filtering plus light networking
ZimaBoard 2 832 provides enormous headroom.
- Normal AdGuard Home hostZimaBoard 2 832
- More VPN/proxy/network servicesZimaBoard 2 1664
Network services integrated with storage/home cloud
Choose ZimaCube for the broader platform, not DNS filtering.
- Integrated home-cloud/network serverZimaCube 2 Standard
No fixed client-count or queries-per-second guarantee is implied. Filter lists, cache, logging, encrypted DNS, upstream latency and co-hosted services all matter.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | AdGuard Home plus lightweight VPN/proxy/network services. | Network-wide DNS filtering, cache, logs and encrypted DNS. |
|
AdGuard Home is unlikely to be the resource bottleneck on this hardware. | Get Now |
| ZimaBoard 2 1664 | A larger networking/self-hosted server including AdGuard Home. | DNS plus more VPN, reverse-proxy and monitoring containers. |
|
16 GB is for the wider networking stack, not AdGuard Home. | Get Now |
| ZimaCube 2 Standard | A home-cloud/NAS that also provides AdGuard Home DNS. | Storage, apps and network services on one platform. |
|
Choose it for storage/app consolidation rather than DNS compute. | Get Now |
What the Press Says
Highlights from trusted reviewers worldwide.
“ZimaCube 2: Not just another NAS, tested with 25TB storage, local AI agents, 4K transcoding, and real homelab workflows.”Read full review
“The ZimaBoard 2 is a compact x86 server board that can be turned into a mini NAS, home server, media box, or self-hosting hub.”Read full review
“ZimaCube 2: A modern, high-performance NAS with plenty of room to grow—built for users who want more than basic storage.”Read full review
“Coverage focused on ZimaCube 2's open hardware foundation, no monthly fee, and self-hosting flexibility.”Read full review
Loved by the Community
Stories and reviews from people who build with Zima every day.
★★★★★
Zima Blade Little yet Powerful
Maybe I am not digital natives but I live with PCs since 12 years old in 1984 when IBM PC clone come to my home. Many years have passed and many operating system I've tried. For me Zima blade and CasaOS was a quantum leap for home PC enthusiast and server lab machine to make me stay curious and relevant for this era.
★★★★★
Very good!!
I use ZimaCube Pro as 5th Proxmox cluster node. It runs several VMs and containers, including a VM with GPU passthrough to run a self-hosted LLM. A specific LXC container runs a Samba server for NAS capabilities using four of six RAID 6 SATA HDDs with ZFS.
★★★★★
Great innovation for mini server!
It is very useful and makes a powerful mini server for many purposes, including university and college students in engineering and electronics. Thank you so much for making this server.
★★★★★
Avaliação ZimaBoard 2
Construí um servidor de uso pessoal. O desempenho está muito bom e funciona perfeitamente onde quer que eu esteja. A surpresa é não dependermos de grandes estruturas para termos nosso próprio servidor de dados. Como iniciante, estou gostando bastante do ZimaOS, pois ele é simples e eficiente.
Frequently asked questions
FAQ topics follow query fan-out around minimum RAM, filter-list memory, DNS cache, query logs, encrypted DNS and whether AdGuard Home needs dedicated hardware. Community reports are used to identify pain points, while upstream docs define actual configuration.
How much RAM does AdGuard Home need?
AdGuard Home upstream does not publish a universal RAM minimum. OpenWrt currently suggests 50 MB free RAM as general router guidance, but that is not an upstream requirement.
Can AdGuard Home run on 512 MB RAM?
For many home workloads, yes in practice, but useful capacity depends on filter size, cache, logs and other services. Do not treat 512 MB as an official guarantee.
Why does AdGuard Home use more RAM after adding filters?
Filter rules must be parsed and held in structures used for matching. Larger or redundant filter lists can increase memory and update-time CPU pressure.
Does the DNS cache use RAM?
Yes. AdGuard Home exposes cache_size in bytes, so the administrator can bound/tune the in-memory DNS cache.
Can query logs cause disk activity?
Yes. Query logging and statistics create ongoing data writes/rotation, which is especially noticeable on small router flash or HDD-based NAS systems.
Does encrypted DNS require more CPU?
Generally yes compared with plain LAN DNS because TLS/QUIC protocol work is added. On modern Zima hardware this is still a light workload for normal homes.
Can ZimaBoard 2 832 run AdGuard Home?
Easily. Its N150 and 8 GB RAM are far beyond normal AdGuard Home needs and leave room for other network services.
Should I use a second AdGuard Home instance?
For DNS availability, a second resolver on another host can be more useful than buying a faster single host because it covers maintenance and failure of the primary server.
What sources and further reading informed this AdGuard Home hardware guide?
AdGuard Home's current Getting Started and Configuration pages define deployment, cache and filtering behavior. OpenWrt provides clearly labelled platform-specific small-router guidance. Current upstream issues and Reddit discussions were used for filter/memory query fan-out, while ZimaOS confirms the Networking app.
