I use pure IPv6 on a bind caching nameserver: 2001:4860:4860::8844; 2001:1608:10:25::1c04:b12f; 2600::1;
Considering the throughput of my exit node and the amount of dns cached, I not leaking as much as you might expect. On Fri, Aug 4, 2017 at 2:38 PM, teor <teor2...@gmail.com> wrote: > >> On 5 Aug 2017, at 00:29, niftybunny <ab...@to-surf-and-protect.net> wrote: >> >> I got lots of "[WARN] eventdns: All nameservers have failed" with my own >> DNS server. With the 4 DNS servers I posted here a few minutes ago, I never >> saw this warning again. > > Apparently this warning happens when you have one DNS server in response > to malformed requests (like ".foo.bar"). > > I would not be too concerned about it if it's followed by: > "[notice] eventdns: Nameserver IP:53 is back up" > > We'll try to work out whats happening and downgrade the warning in these > cases: > https://trac.torproject.org/projects/tor/ticket/23113 > > For client privacy and performance, it's best to have a local cache or > caching resolver first in the list. > > For reliability, it's best to have another two entries in the list on > unrelated infrastructure (for example, one at the ISP, and one > elsewhere). > > T > > -- > Tim Wilson-Brown (teor) > > teor2345 at gmail dot com > PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B > ricochet:ekmygaiu4rzgsk6n > xmpp: teor at torproject dot org > ------------------------------------------------------------------------ > > > > > _______________________________________________ > tor-relays mailing list > tor-relays@lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays