rdme

4 ms·

1. 31.▲
   by rdme 6mo ago

   because I clicked reply on the wrong one and you can't delete it...
2. 32.▲
   by rdme 6mo ago

   Is it possible you didn't start it as root ( sudo numa install)? Does dig {mygivenname}.numa @127.0.0.1 return 127.0.0.1 ? What OS are you on? Maybe you report it as an issue?
3. 33.▲
   by rdme 6mo ago

   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!
4. 34.▲
   by rdme 6mo ago

   Yes sir! The query log is at GET /querylog (or on the dashboard) shows every request with domain, type, path (forwarded/recursive/cached/blocked) and latency
5. 35.▲
   by rdme 6mo ago

   Thanks! If you hit any issues during setup, feel free to open an issue — happy to help debug. The dashboard at localhost:5380 (or at https://numa.numa )
6. 36.▲
   by rdme 6mo ago

   Yes, it is configurable as a list https://github.com/razvandimescu/numa/blob/main/numa.toml#L4... There's also a per-domain allowlist and you can pause/unpause blocking from the dashboard or AP
7. 37.▲
   by rdme 6mo ago

   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.
8. 38.▲
   by rdme 6mo ago

   Thanks! Let me know how it goes.
9. 39.▲
   by rdme 6mo ago

   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. I wrote about the DNSSEC implementation here: https
10. 40.▲
    Show HN: I built a DNS resolver from scratch in Rust – no DNS libraries(github.com)

    115 points by rdme 6mo ago|68 comments