Pi-hole v6

Original Article ↗ Hacker News Discussion ↗

Overall reception & common use cases

  • Many commenters call Pi-hole “killer”/essential, often running for years on low-end hardware (Pi Zero, Pi 3) with minimal maintenance.
  • Main perceived benefits: massive reduction in ads/tracking, “clean” web on all devices, fewer annoyances on smart TVs and Android TV/Shield, and better subjective performance.
  • Some use Pi-hole primarily as a second layer behind uBlock/Brave; others rely on it for devices where browser blockers aren’t available (TVs, consoles, IoT).

Pi-hole vs alternatives (uBlock, AdGuard Home, NextDNS, Technitium, etc.)

  • uBlock is seen as complementary, not a replacement (browser-only vs. network-wide).
  • AdGuard Home is praised as more polished, with native DoH and multi-OS support; some migrate to it, others return to Pi-hole due to reliability.
  • NextDNS and similar SaaS resolvers are liked for ease, mobility, and per-device profiles, but criticized for latency, dependency on third party, missing custom blocklists, and client app stagnation.
  • Technitium is valued for richer DNS features (split-horizon, Tailscale integration) and DoH support.

DoH/DoT, privacy, and network control

  • Strong interest in encrypted upstream DNS from Pi-hole (to avoid ISP snooping), usually via dnscrypt-proxy, cloudflared, or external DoH servers.
  • Some dislike DoH as “tunnel everything over HTTP,” preferring DoT; others note DoH’s value in hostile networks where DNS/853 are blocked.
  • Concern about devices bypassing filtering with DoH or hardcoded DNS; suggestions include firewall rules redirecting/denying port 53 and VLAN isolation.

Performance, reliability, and deployment patterns

  • Debate over DNS latency: some say it’s a major perceived-speed factor; others think modern page bloat dwarfs a few extra ms. Local caching (Pi-hole, router, unbound) is widely recommended.
  • Reliability issues: SD card corruption after power outages vs. reports of years-long uptime; mitigations include logging to RAM, better SD cards, UPS, or running on routers/servers/VMs.
  • Multiple Pi-holes or high-availability setups (Kubernetes, multiple Pi4s, Proxmox, OpnSense) are common for redundancy.

Pi-hole v6 features and missing capabilities

  • New web UI with Basic/Expert modes is welcomed as better for non-experts and family setups.
  • Integrated REST API and embedded web server (no lighttpd/PHP) are seen as big wins for automation and simplification, though one commenter dislikes further monolith-izing FTL.
  • Still-missing or confusing features people want:
    • Native, simple DoH/DoT config in the UI.
    • “Dry run”/audit mode to show “would be blocked” items.
    • Easier per-client/group behavior when the router hides clients.
    • Built-in config and stats sync across multiple Pi-hole instances.
    • DNS views / subnet-based answers, wildcard local DNS, richer DHCP options.

Smart TVs, IoT, and the ad arms race

  • Many keep TVs off the network or on isolated VLANs; others rely on Pi-hole/AdGuard to reduce telemetry and UI ads.
  • Recognition that DNS blocking cannot stop everything: apps may share domains between content and ads (e.g., YouTube), or adopt DoH/baked-in IPs. Pi-hole can’t reliably block YouTube video ads without collateral damage.
  • Workarounds include alternative clients (ReVanced, Kodi, separate streaming boxes), VLAN firewalls, and occasionally embracing “dumb” displays plus external players.

Censorship, ethics, and trust

  • Some use Pi-hole and firewall rules to block entire platforms (Meta, X) or ASNs/countries; others frame this as home censorship, likely to incentivize VPN usage.
  • Debate over trusting software from Russia/other adversarial jurisdictions (e.g., AdGuard Home binary) vs. building from source and judging code rather than nationality.
  • Several note that vendors (ISPs, TV makers, ad tech) increasingly rely on surveillance revenue, reinforcing the appeal of self-hosted filters like Pi-hole.