Let’s explore the challenges behind the first two. an authority, which maintains information about a domain.a resolver, which contacts authorities to answer queries.a query tool like dig(1), to send queries and print responses.a protocol encoder, to serialise outgoing DNS messages.a protocol decoder, to understand incoming DNS messages.When we build a DNS implementation, that might mean: This is how your browser knows to contact 107.191.57.160 when you go to. The most familiar example of these is IP addresses (the information) and hostnames (the names). Zero-copy views ( hg-v1, hg-v2, hg-v3, hg-v4)ĭNS is a distributed database that stores information in a hierarchy of names.Rust already has a mature DNS implementation that I’ve heard wonderful things about, and there’s a long way to go before nonymous approaches anything resembling feature-complete or production-ready.īut bore(1) is useful enough that I actually reach for it in 90% of the situations I would have previously used dig(1)… Most people don’t realise the opposite of anonymous is nonymous - the hacker known as “Alex”, 2020 Here’s a post about what I’ve learned so far while writing nonymous, an embedded-friendly DNS library with #! and no-alloc support, and bore(1), a CLI tool for sending DNS queries.

This project started out as a vehicle for learning Rust, but the more I learned, the more challenging goals I was able to set, to the point where I can see its potential to become useful in its own right. I’ve been writing a DNS implementation in Rust. ~/talks/ nonymous + bore(1): DNS toys for Rust Nonymous + bore(1): DNS toys for Rust | delan azabani Delan Azaban i ~/ :

Any Other Name by Alex Nonymous