Dear Twisted people, I've been taking a good look at twisted.names as a sever after checking twisted-infra/braid/services/names and how the zones are saved. Basically, I wonder what the state-of-afairs of running DNS with twisted is. By checking the code I see a couple things like: * That zone transfers are enabled by default and open to any host and only subclassing would help override that (it is the case on twistedmatrix.com btw). * Comments saying how some things are not RFC-compliant, but not how. * That DNSSEC is not implemented Besides the 1st point which could be a ticket (should I open it?), the other points appear to be somewhat documented in the open tickets: https://twistedmatrix.com/trac/query?status=assigned&status=new&status=reopened&component=names&group=priority&max=200&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=milestone&order=priority But I wonder if there is something like a roadmap that I haven't seen or a very specific way to start helping on this front. Basically, I'd hate to start working on sth and it overlapping with someone else's work ;). I checked a couple tickets, and see that there is definitely a need for some cleanup, e.g. this one appears to be ready for closing https://twistedmatrix.com/trac/ticket/5048 as it is marked as duplicate of a closed ticket. Also, I recall this PR from early summer, which appears to have been OK'd but is blocked by some failure in appveyor + buildbot: https://github.com/twisted/twisted/pull/954 Thank you for any pointers, and thank you for Twisted! -- Evilham