Section 4 of 5
Five servers, and what each was built to be good at
The implementations, compared honestly.
BIND, NSD, Unbound, Knot and PowerDNS made different choices about which of the two jobs they do and where the zone data lives. Four pieces on the field, including the design that gave this domain its name.
4 pieces in this section
- 01Five servers, and what each was built to be good atBIND, NSD, Knot, Unbound and PowerDNS solve overlapping problems with different priorities, and the differences are architectural.
- 02tinydns, and the file it answers fromThe design that gives this domain its name answered from a single prebuilt constant database and refused to recurse in the same process.
- 03Why the two jobs were split apartKeeping authoritative service and recursion in separate processes removed a whole class of failure, and the field eventually agreed.
- 04What DNSSEC does, and what it does notIt proves an answer came from the zone; it does not make the answer private or the zone correct.