FEDIDEVS

So, dnsdist is smaller but not yet small enough.

#FOSDEM (end of the day)

Obvious things (making some code optional, tuning the default configuration, compiling with more aggressive options, packing the executable) did not really help.

One of the problems: most of the memory was used by OpenSSL, not by dnsdist itself. (but wolfSSL was not really better)

Lua (used to adapt dnsdist behavior) was also a big memory user.

#FOSDEM

The goal was to shrink #dnsdist to fit in a CPE router, using OpenWRT on small hardware.

#FOSDEM

And to end the day at the #DNS devroom, "Honey, I shrunk DNSdist" by @habbie (replacing @rgacogne, the maintainer who is sick without even the fault of the FOSDEM)

Disclaimer: #dnsdist is used by the public DNS resolver {doh,dot,doq}.bortzmeyer.fr

#FOSDEM

Replaced the old cooperative scheduling with per-thread libuv loops. "The kernel is smarter than we are"

#FOSDEM

"How to make BIND 9 fast(er)" by @ondrej

New locks: https://dl.acm.org/doi/10.1145/2442516.2442532

Use of userspace RCU (Read-Copy-Update)

Making some data structures lock-free

#FOSDEM

And proving that you own an IP network?

#FOSDEM

For proving you own a Web site;, is a TXT in the DNS better than a HTML file in the Web site? Pros and cons?

#FOSDEM

There is an Internet-Draft for that: https://datatracker.ietf.org/doc/draft-ietf-dnsop-domain-verification-techniques/

See also https://keyoxide.org/

#FOSDEM

"Prove website, domain, and network ownership" by Mark Overmeer

Just do like Oracle, add TXT records at the apex. https://mastodon.gougere.fr/@DNSresolver/113929489912379335

#FOSDEM