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
  • @Bonderosa@lemmy.worldOP
    link
    fedilink
    English
    5•
    edit-2
    6 hours ago

    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.

    • @Placid@lemmy.world
      link
      fedilink
      English
      11•
      edit-2
      4 hours ago

      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.

      • @Bonderosa@lemmy.worldOP
        link
        fedilink
        English
        0•4 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

    • Jo Miran
      link
      fedilink
      English
      9•5 hours ago

      I find the AI disclosure rules for this community to be well thought out and reasonable. Please follow them. It doesn’t take very long to put together the compliant tags and disclosure text.