I'm the developer of JustDNS, a self-hosted filtering DNS resolver for your whole network. I built it because I wanted more than a block count. I wanted to see which companies my devices actually talk to.

What it does

  • Blocks ads, trackers and malware, like Pi-hole or AdGuard Home.
  • Privacy dashboard that attributes DNS traffic to the companies behind it, with a per-device breakdown and a world map of where answers resolve. You can block a company for a single device or the whole network.
  • Encrypted upstreams (DNS-over-TLS) by default, plus DNSSEC validation.
  • Per-device and per-group policies, user accounts with roles and TOTP.
  • Optional multi-node high availability.

Running it

  • Docker / docker compose, or a one-click Unraid Community Apps template.
  • AGPL-3.0, no cloud account, nothing phones home.

Repo: https://github.com/bonderaustriaAT/JustDNS

It's still young, so I'd genuinely like feedback from people running Pi-hole or AdGuard today: what would make you switch, and what's missing? Happy to answer questions.

EDIT:

AI Disclosure:

  • Design - Most 70% AI
  • Implementation - Hints
  • Testing - Assisted
  • Documentation - Pair
  • Review - Assisted
  • Deployment - Assisted
you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 5 hours ago (1 child)

Is the company id by AS number? If so I think that would always show the hosting provider but not the actual operator. Like anyone hosting on GCP would be using a Google AS, or do I have that wrong?

  • source
  • hideshow 1 child comment
  • [–] [S] 1 point 5 hours ago

    The company attribution is domain-based a compiled in catalogue mapping registrable domains to the operator (connect.facebook.net to Meta, etc.), so hosting AS doesn't matter there. The limitation is that it's a curated set not exhaustive. The world map is the ASN part you mean: offline IP-to-ASN, which does show the host (GCP, Cloudflare). So "who" comes from the domain, "where" from the AS.

  • source
  • parent