tordnsel for Debian ------------------- The package installs a systemd unit that is neither enabled nor started, because TorDNSEL can't run until its zone is configured. Edit /etc/tordnsel.conf (at least ZoneOfAuthority, DomainName and SOARName), then run systemctl enable --now tordnsel Tor's control port ------------------ TorDNSEL works with Debian's tor package as it is installed: /etc/tordnsel.conf points it at tor's control socket, /run/tor/control (and, for active exit tests, its SOCKS socket, /run/tor/socks), and the unit adds the tordnsel user to the debian-tor group, which may use them (SupplementaryGroups=debian-tor). No change to /etc/tor/torrc is needed. TorDNSEL authenticates with tor's cookie (SAFECOOKIE), which Debian's tor writes to /run/tor/control.authcookie, readable by the same group. While connected, TorDNSEL turns on FetchUselessDescriptors in tor, so that tor downloads every relay descriptor. If tor is restarted, TorDNSEL reconnects within a minute. To use a tor running elsewhere, set TorControlAddress (and TorSocksAddress) to its ControlPort (and SocksPort), e.g. 127.0.0.1:9051. Statistics ---------- The statistics socket, /run/tordnsel/statistics.socket, may be used by the tordnsel user and group only; add whatever reads it (e.g. the Cacti script in /usr/share/doc/tordnsel/examples) to the tordnsel group. Firewall -------- TorDNSEL answers on DNSListenAddress over both UDP and TCP; let both through. UDP responses are rate limited per client network (DNSRateLimit). -- Masayuki Hatta Thu, 05 Nov 2026 10:00:00 +0900