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

all 22 comments

sorted by: hot top controversial new old
[–] 62 points 6 hours ago

"Contributors: Claude"

Please refer to rules 7 and 8 of this community.

  • source
  • [–] 19 points 6 hours ago (6 children)

    How much Claude is in this?

  • source
  • hideshow 6 child comments
  • [–] [S] 6 points 5 hours ago* (last edited 5 hours ago) (4 children)

    The design, architecture and decisions are mine. I use AI as a tool (mostly OpenCode, sometimes Claude) for structure and the occasional code snippet, and most of all for the UI, since design isn't my strength.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 11 points 3 hours ago* (1 child)

    Your commit patterns suggest you use AI for more than you share here. A feature lands, then 15-60 minutes later a fix commit occurs. This is pretty typical when a second agent reviews the work of the first. I run the same pattern myself.

    Here are some examples that I see just on Nov 14:

    • the HA cluster rolling update (22 files, about 2,500 lines at 17:11, review fixes for a start race, downgrade protection and worker hardening at 18:06),

    • GeoIP enrichment (19:30, review fixes at 19:43),

    • and the world map and geo-watch (1,650 lines at 22:00, review fixes at 22:14).

    These are backend features (cluster sync, crypto, update worker). Nobody writes that much Rust by hand that fast.

    Tons of comments like an AI would write. You're certainly using AI to write tests, too.

    It's okay to use AI for hobby projects, but when you're offering a product to the public, the public deserves to know the products provenance.

  • source
  • parent
  • hideshow 1 child comment
  • [–] [S] 0 points 3 hours ago

    Like I mentioned in the post, I do use AI to assist with testing, comments, code reviews, and coordinating parts of the project which is pretty standard these days to catch edge cases early. The crazy commit speed, though, is mostly because I build and test everything locally on my private Gitea server first and then push it step bystep to GitHub which makes the timestamps look way faster than they actually were.

    To keep things completely transparent going forward I’m going to drop the Gitea middleman and push straight to a dev branch on GitHub so everyone can see the real time progress.

    In the next days I will publish on the github the complete AI usage so its more transparent to everybody

  • source
  • parent
  • [–] 16 points 5 hours ago (4 children)

    What does this offer that the other major systems don't already provide?

    1. Pihole
    2. Adguard home
    3. Technitium
    4. eBlocker OS
  • source
  • hideshow 4 child comments
  • [–] [S] 3 points 4 hours ago (3 children)

    For basic ad and tracker blocking the overlap is large and AdGuard Home covers most of it . JustDNS isn't trying to redo that part Three things set it apart:

    Attribution. It groups queries by the company behind the domains, not just by domain, and does it per device. You can block a company across all its domains and CNAMEs, for one device or the whole network, in a single action.

    Built-in HA. Pi-hole and AdGuard Home have no native high availability you add a third-party sync tool. JustDNS replicates config and query state across nodes over an authenticated channel so one node failing doesn't take DNS down.

    DNS only. No HTTPS interception, unlike eBlocker. No CA to trust for the filtering, nothing terminating your TLS. One container, local only, no account, config encrypted at rest.

    Technitium is a full DNS server (zones, DHCP, scripting), a different scope(in the moment). JustDNS is a filtering resolver focused on attribution and per-device policy.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 3 points 3 hours ago (2 children)

    Why is this down voted? I think it's good to hear explanations to see if OP (or anyone) understands what they're building and what issues they look to solve.

    Good to know there's some competency.

  • source
  • parent
  • hideshow 2 child comments
  • [–] -5 points 2 hours ago

    Whenever you see the word A*, you have to automatically downvote the whole post and smack its op around whenever you see them. It doesn’t matter if it has anything genuinely useful, as long as Clau*** or Cod** is somewhere in the post or the repo on GitHub.

  • source
  • parent
  • [–] 6 points 6 hours ago* (4 children)

    Interesting, thanks for sharing.

    I see comparisons to pihole, but how does it compare to Technitium, especially since it supports clustering.

    Honestly glad you are doing this, because I was a bit bummed that the only DNS filter I found that easily supported HA was written in C# (personal preference/prejudice). I'll give this a go when I find some time to ϲнαπgє τнє ⲅμππίπg ϛψϛτєϻ

  • source
  • hideshow 4 child comments
  • [–] [S] -3 points 6 hours ago (3 children)

    Thanks! Fair question, and Technitium is the right comparison once you want more than Pi-hole.

    Honest framing: Technitium is a full DNS server (authoritative zones, DHCP, scripting, the lot) and it's mature and battle-tested. If you need a complete DNS platform, it's hard to beat. JustDNS is narrower on purpose. It's a filtering resolver built around one idea: showing which companies your devices actually talk to, with per-device attribution, a world map, and the ability to block a company for a single device or the whole network, plus per-device and per-group policies. So it's less "DNS server" and more "privacy-focused filter with a dashboard."

    On clustering/HA: JustDNS has optional multi-node HA, but it works differently from zone replication. Nodes share one config and query state over an authenticated channel (HKDF-SHA256 + ChaCha20-Poly1305), up to a handful of nodes, with a cluster-wide update that rolls them together. It's aimed at "run two or three boxes, keep them identical, no single point of failure," not authoritative zone transfer.

    And yes, it's Rust, which is partly why I started it. It's young though, so Technitium wins on maturity and breadth today. If you give it a go I'd genuinely like to hear where it falls short for your setup.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 11 points 5 hours ago (2 children)

    At least the first section of this response sounds like it was AI generated.

  • source
  • parent
  • hideshow 2 child comments
  • [–] [S] -3 points 5 hours ago (1 child)

    I'll take that as a compliment on the structure though I actually wrote the whole thing myself

  • source
  • parent
  • hideshow 1 child comment
  • [–] 16 points 5 hours ago

    Honest Framing: it sounds like you're not being truthful or you've used/read AI so much that you've started to emulate the linguistic patterns. This isn't accusatory, I've found myself typing similar things and I find it infuriating in my own life. My honest advice, be more up front with AI usage in this forum. It buys a lot of good will.

  • source
  • parent
  • [–] 8 points 5 hours ago (1 child)

    Most people would just ship their logs to something like Graylog if they need this type of analysis.

  • source
  • hideshow 1 child comment
  • [–] [S] -4 points 5 hours ago

    Fair point, but analysis isn't really the goal. Graylog shows you logs, it doesn't resolve DNS, block anything, or enforce a per-device policy. JustDNS is the resolver itself: the company attribution is a byproduct, the actual job is acting on it. Block a company for a single device or the whole network, with per-device and per-group rules.

    The real reasons it's its own thing: everything stays local, no query history shipped off to another system, no external data at all, which is kind of the whole point for a privacy tool. On top of that, DNSSEC, encrypted client DNS (DoT/DoH), and optional multi-node HA so it isn't a single point of failure. The attribution and the world map are built in, with no log pipeline, parsing or GeoIP setup to maintain.

    So Graylog is great if you just want to look at logs. JustDNS is for when you want the resolver to see it, show it, and actually do something about it, without handing your full DNS history to yet another box.

  • source
  • parent
  • [–] 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 4 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