Ondřej Surý

BIND 9 consists of a huge and old codebase. In this talk, I would like you to show all the available tools that we use on regular basis to improve, refactor and make the BIND 9 code safer. I'll show the examples of various Google/LLVM Sanitizers, cppcheck, LLVM scan-build and semantic patching using coccinelle.

BIND 9 is now 17 years old, the latest stable version 9.12 was releases in December and the BIND 9 Team has adopted changes to adapt to the ever change Internet landscape.

In this talk, I will present BIND 9 colorful past, the current state of development, and the changes that BIND 9 Team has adopted to cope with modern DNS. I will talk about the changes in the development model, release cycles, and also about the planned features that will help BIND 9 Team to be more nimble in adding new features, fixing old issues, spending less time on maintenance, while ensuring the stability for existing users. I believe that existing BIND 9 users will be thrilled.

The Knot DNS Resolver is a caching full resolver implementation written in C and LuaJIT, including both a resolver library and a daemon. Modular architecture of the library keeps the core tiny and efficient, and provides a state-machine like API for extensions. There are three built-in modules - iterator, cache, validator, and many external.

The Lua modules, switchable and shareable cache, and fast FFI bindings makes it great to tap into resolution process, or be used for your recursive DNS service. It's the OpenResty of DNS.

The server adopts a different scaling strategy than the rest of the DNS recursors - no threading, shared-nothing architecture (except MVCC cache that may be shared). You can start and stop additional nodes depending on the contention without downtime.