>> djbdns has been broken for ~20 years -- no AXFR, no EDNS0, no >> TCP/53, no DNSSEC, no TSIG, etc, etc -- > >I'm may be too picky but these cases are different: djbdns misses some >features, some mandatory (TCP), some facultative (DNSSEC). It is not >the same thing as a bug (violation of the standard).
Actually, djbdns does TCP and AXFR perfectly well, albeit using a separate program from the one that handles UDP queries. I swapped secondaries with a BIND site for over a decade using its AXFR, perked up with a little perl script that looked at the SOAs to limit the useless AXFRs. It doesn't do EDNS0 or DNSSEC, partly because Dan is stubborn, but mostly because it's been abandonware for almost 20 years. I patched for a while but gave up and switched to unbound and nsd. R's, John _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
