Replying to Avatar Matt Corallo

For wallets wanting to get a head start on implementing human-readable bitcoin names, here’s a library that handles all the DNS parts!

* resolves against a local (/remote) TCP/53 resolver

* resolves against a DoH/DoT resolver

* creates/validates proofs

https://docs.rs/dnssec-prover/

It can even be run in WASM on a web page (and resolve via DoH directly)!

https://http-dns-prover.as397444.net

Avatar
Kristaps K. 1y ago

Why only tcp/53, not also udp/53?

Reply to this note

Please Login to reply.

Discussion

Avatar
Matt Corallo 1y ago

I mean it could work over that too but then you have to handle truncation and tcp fallback and that’s annoying

Avatar
Kristaps K. 1y ago

UDP is kinda default for DNS mostly.

Avatar
Matt Corallo 1y ago

Default yes but servers MUST support both, for fallback :). When talking to an authoritative server, UDP is important, but when talking to a recursive resolver, who cares?