I now have AdGuard Home configured as the primary DNS server that's handed out by my DHCP server, and it routes queries for "naked hostnames" and my internal domain to docker-dnsmasq. After a little research and testing in docker, I couldn't figure out how to set up multiple DHCP scopes and static DNS entries, so I opted to keep docker-dnsmasq in place. It looked pretty slick, but I already run my own DNS/DHCP server using my docker-dnsmasq project. It's based on software we use for our public AdGuard DNS servers, and both share a lot of code. It operates as a DNS server that re-routes tracking domains to a “black hole”, thus preventing your devices from connecting to those servers. After you set it up, it'll cover ALL your home devices, and you don't need any client-side software for that. I don't recall exactly where I instantly opened a new tab Google tab to search for it and quickly lost track of the source.ĪdGuard Home does its magic blocking ads at the network level by acting as a DNS server that "black holes" queries for known ad/tracking domains.ĪdGuard Home is a network-wide software for blocking ads & tracking.
A week or two ago, I had seen a reference to AdGuard Home as an alternative to Pi-Hole somewhere.
0 kommentar(er)
