Since I needed it to be my primary DNS, I also added: recursive resolution from root nameservers, DNSSEC chain-of-trust validation, ad blocking (385K+ domains), and LAN service discovery.<p>I wrote about the DNSSEC implementation here: <a href="https://numa.rs/blog/posts/dnssec-from-scratch.html" rel="nofollow">https://numa.rs/blog/posts/dnssec-from-scratch.html</a>
It's now my daily system DNS.
Single binary (~8MB), macOS/Linux/Windows.<p>`sudo numa install`
Very interesting project! I have a couple of questions. With all the default blocked domains loaded, what is the average memory usage? Currently, I am using Pi-hole on a low memory single board computer. Is it possible to use this instead of Pi-hole? If so, I’d like to use it for all of my devices."
With 390K blocked domains: ~31MB total process footprint.
Breakdown:
- Blocklist: 23.4MB (390K domains)
- Cache: 3.8MB (4.4K entries)
- Query log, SRTT, runtime: ~4MB<p>It binds to 0.0.0.0:53 by default, so just point your devices' DNS to the board's IP
Romanian project. Instant upvote. Great work
Thanks! If you hit any issues during setup, feel free to open an issue — happy to help debug. The dashboard at localhost:5380 shows what's happening in real time.
It's neither here nor there but can I ask about the name? I only ask because when I see "numa" in relation to computing I immediately think "Non-Uniform Memory Access".<p>Very cool project by the way. I wonder how this would run on an OpenWRT device.<p>I see in your install.sh that you support Linux and Darwin/MacOS, do you think there would be any major hurdles in supporting FreeBSD?
also in romanian nume = name(dns) and I also get the easter egg of that well known Romanian song numa numa :) <a href="https://www.youtube.com/watch?v=YnopHCL1Jk8" rel="nofollow">https://www.youtube.com/watch?v=YnopHCL1Jk8</a><p>On OpenWRT — it's musl-based Linux so the binary should run the arm one would need a crosscompile
Free BSD can be done (pr's welcome?)
On the web site, it's named after the second King of Rome
I have a couple of projects that once a month need to run a few million dns lookups as quickly as possible. I'm tempted to try this just to see how it performs and if it breaks.
The interface looks vibecoded. I have no problem with people vibecoding things. In fact, I have zero frontend skills, so I rely on AI to be able to make easy-to-use interfaces. However, I feel like this should be clearly and prominently displayed in the project page.<p>Furthermore it is a little off-putting to see a vibecoded UI because I have very little confidence that the rest of the backend code is not vibecoded. I know I am possibly being unfair, but this is how it looks to me. If the developer tells me they didn't use AI at all, I would believe it.
It definitely is and you can see it in the git commits. The DNS wire protocol parser was the original learning project I wrote to understand the spec. Later features (recursive resolver, DNSSEC validation, the dashboard) were built with the help of AI
I dont get this criticism at all, would you prefer someone write a shittier UI? And since when were people writing amazing bug free software before hand where not being vibe coded meant you could trust its good software?<p>I guess to be fair, beforehand no body would be attempting this kind of thing and releasing it unless they knew what they were doing
Given the state of webdev it is not a surprise. LLMs are my rubber gloves when working with web technologies.
Nice idea. To test I ran a simple nextjs on port 3000. Added the service via the dashboard.
However, when I visit the url, (using chrome latest version), <a href="https://{mygivenname}.numa/" rel="nofollow">https://{mygivenname}.numa/</a> I hit a DNS resolution fail error.
If I do not use a trailing '/' then it is going to google search for {mygivenname}.numa and shows me some search results. Should I open an issue?
What's the reason you're not using hickory? Or was that the LLMs choice? Genuinely curious
The first thing I look at in new DNS code is whether it’s vulnerable to DNS name compression loops. This code passes the test! However it’s vulnerable to dots embedded in labels: it doesn’t escape bytes properly when converting from wire format to text.
Thanks for pointing this out! I’ve created <a href="https://github.com/razvandimescu/numa/issues/36" rel="nofollow">https://github.com/razvandimescu/numa/issues/36</a>
How does one handle dots embedded in a label ? Isn’t that not valid?
Same hack here ; I have no DSN running by default - much more handy than having to set up nginx as it has no opinion on the targeted infrastructure. And the bonus point is that you can see every sneaky request that happens when you browse ; so another side-project connected to this is to make an inventory and policy filter
feature request: libnuma so i can use it programmatically with configuration. also, multiple user defined blocklists.
Multiple blocklists already work -<a href="https://github.com/razvandimescu/numa/blob/main/numa.toml#L44" rel="nofollow">https://github.com/razvandimescu/numa/blob/main/numa.toml#L4...</a>
The pieces are already there for libnuma, it could be done, would you share what use case you have in mind?
I have a project that requires DNS lookups and block ads. I am going to try this for it.
How is to compare to AdGuard? If it gets those features I would be switching over.
Cool idea, every developer running apps in dev on their machine knows this pain for sure. I'll give it a spin and let you know how it goes!
Nice work. What made you choose this license?
I think I need to give this a go. Cool project.
very interesting. how does the blocklist work? can one manage the lists? like StevenBlack or others.
Yes, it is configurable as a list
<a href="https://github.com/razvandimescu/numa/blob/main/numa.toml#L44" rel="nofollow">https://github.com/razvandimescu/numa/blob/main/numa.toml#L4...</a><p>There's also a per-domain allowlist and you can pause/unpause blocking from the dashboard or API.<p>Here's how the resolution pipeline looks like: <a href="https://numa.rs/blog/posts/dns-from-scratch.html#the-resolution-pipeline" rel="nofollow">https://numa.rs/blog/posts/dns-from-scratch.html#the-resolut...</a>
nice
Great idea, pity about the slop.
we need a <i>[slop]</i> flag in the headlines
[flagged]
[flagged]
[flagged]
[flagged]
Actually, if you point a container's DNS at the host (dns: [host.docker.internal] in compose), it works for resolution + ad blocking for the reverse however, I've added it on the radar, thanks!
I don't want to hijack the thread, because that's a cool project.<p>Still, if you're looking for something that "just works" and is widely used, have a look at caddy.
[flagged]