Maza Ad Blocking
Self-HostedDNS-based ad blocker for Unbound and Pi-hole
Overview
Maza Ad Blocking is an open-source DNS ad blocker that integrates with Unbound or Pi-hole to block ads, trackers, and malicious domains at the network level. It uses curated blocklists with automatic updates, supports custom whitelists/blacklists, and works across all devices without client-side software. Deployment involves installing via a script and configuring your DNS server (e.g., adding a zone file to Unbound or a custom list to Pi-hole), making it ideal for self-hosters seeking privacy and control over their network’s ad filtering.
Self-Hosting Resources
Below is a reference structure for docker-compose.yml.
⚠️ Do NOT run blindly. Replace placeholders with official values.
version: '3'
services:
maza_ad_blocking:
image: <OFFICIAL_IMAGE_NAME>:latest
container_name: maza-ad-blocking
ports:
- "8080:<APP_INTERNAL_PORT>"
volumes:
- ./data:/app/data
restart: unless-stopped Key Features
- Integrates with Unbound and Pi-hole DNS servers
- Curated blocklists with auto-updates
- Custom whitelist/blacklist support
- Network-wide ad/tracker blocking
Frequently Asked Questions
? Is Maza Ad Blocking hard to install?
Installation is simple via its official script, but it requires an existing Unbound or Pi-hole setup. You’ll need to edit DNS config files (like Unbound’s zone file) or add a custom list to Pi-hole, which may require basic command-line knowledge.
? Is it a good alternative to AdGuard DNS?
Yes, for self-hosters—Maza is open-source and integrates with your own DNS server, giving full control over blocklists and data. Unlike AdGuard DNS (proprietary), it doesn’t rely on external services, enhancing privacy and customization.
? Is it completely free?
Yes, Maza Ad Blocking is 100% open-source and free to use. There are no paid tiers or subscriptions; you only need to host it on your existing DNS infrastructure.
Top Alternatives
People Also Ask about Maza Ad Blocking
Tool Info
Pros
- ⊕ Privacy-focused (no external service dependency)
- ⊕ No client-side software required
- ⊕ Lightweight resource usage
Cons
- ⊖ Requires existing Unbound/Pi-hole setup
- ⊖ Needs basic command-line/config editing
- ⊖ Limited to DNS-level blocking (misses some in-page ads)