docs VS AdGuardHome

It's a DNS proxy, like pi-hole, but it seems a lot more powerful than Pi-hole that is basically just a configured dnsmasq server to be user-friendly.

https://docs.pi-hole.net/

I highly recommend the documentation or this video (which also has a blog) that I followed.

Protip: Setup a DNS Sinkhole on your network and you can easily block Vizio and other devices from calling home to update. https://docs.pi-hole.net/

version: "3" # More info at https://github.com/pi-hole/docker-pi-hole/ and https://docs.pi-hole.net/ networks: dns_net: driver: bridge ipam: config: - subnet: 10.2.0.0/24 services: pihole: depends_on: [unbound] container_name: pihole image: pihole/pihole:latest hostname: pihole networks: dns_net: ipv4_address: 10.2.0.100 ports: - "5335:53/tcp" - "5335:53/udp" - "7000:80/tcp" environment: TZ: ${TZ} WEBPASSWORD: ${PWD} FTLCONF_LOCAL_IPV4: ${HOST_IP} # Set to server's LAN IP, used by web block modes. PIHOLE_DNS_: 10.2.0.200 # Upstream DNS server(s) for Pi-hole to forward queries to, separated by a semicolon DNSMASQ_LISTENING: all # "Listen on all interfaces, permit all origins" # Volumes store your data between container upgrades volumes: - /var/lib/docker/volumes/pihole/etc-pihole:/etc/pihole - /var/lib/docker/volumes/pihole/etc-dnsmasq.d:/etc/dnsmasq.d healthcheck: disable: true restart: unless-stopped unbound: # https://github.com/MatthewVance/unbound-docker container_name: unbound image: mvance/unbound:latest hostname: unbound networks: dns_net: ipv4_address: 10.2.0.200 ports: - "${HOST_IP}:53:53/udp" - "${HOST_IP}:53:53/tcp" healthcheck: disable: true restart: unless-stopped

Absolutely. Check out the Pi-Hole documentation here: https://docs.pi-hole.net/

See https://docs.pi-hole.net/

Also AdGuardhome will use optimistic caching, which is great.

https://github.com/AdguardTeam/AdGuardHome/discussions/4002#...

The main repo is GPLv3: https://github.com/AdguardTeam/AdGuardHome

They already have many other commercials products and I guess also the default filter rules are very good because of their experience in the domain.

But I think you can use it completely without the AdGuard servers and use other filter list sources.

How it compares to let's say AdGuard Home? Seems similar https://github.com/AdguardTeam/AdGuardHome

Adguardhome - Clients identification issue

You can check this documentation if you want to investigate further: https://github.com/AdguardTeam/AdGuardHome/wiki/Hosts-Blocklists

I'm using adguardhome v0.107.42 openwrt snapshot on linksys wrt1900ac v2, but when using DoH it won't resolve upstream DNS, but DoT is works perfectly OK, I've already set allow_unencrypted_doh to true in config .yaml file as per instruction here

AdGuard Home?

https://github.com/AdguardTeam/AdGuardHome

Regarding open source, AdGuard DNS actually is:

How does this compare to adguard home [ https://github.com/AdguardTeam/AdguardHome ] ??

Have you looked at AdGuard Home - Configuring clients?