[tor-relays] lets stop using central big DNS resolvers (Google, Level3, OpenDNS, Quad9, Cloudflare)

[Tyler Durden]

All our nodes are using a local DNS caching server and only use google
as a fallback.
The situation is very unlikely to change unless there is a major player
on "our side" which offers a free, censorship-free, resilient and stable
DNS Service.


Greetings
nusenu:
> Dear Exit Relay Operators,
> 
> I'd like to invite you to check your exit's DNS resolver by 
> having a look at the following list of exits using resolvers
> outside their AS (especially if it is Google, OpenDNS, Quad9 or Cloudflare).
> 
> You can search the list for you contactinfo, relay nickname or relay fingerprint (first 8 characters):
> 
> https://gist.github.com/nusenu/cb766ff7945fafd9f90ee7f211a2508f#file-tor-dns-april-2018-txt
> 
> 
> I extended the "DNS on Exit Relays" section in the Tor Relay Guide
> to include specific instructions what is recommended for Tor exit operators with 
> regards to DNS on exit relays.
> 
> https://trac.torproject.org/projects/tor/wiki/TorRelayGuide#DNSonExitRelays
> 
> If you found yourself on the list above and changed your DNS to a local (same host or same AS)
> resolver or found a false-positive, please drop me an email (off-list is also ok).
> 
> 
> The goal is to be bellow the following thresholds within one year:
> - not have any single remoteAS entity control more than 10% exit capacity
> - reduce the overall remoteAS share to bellow 20% exit capacity
> 
> the longer version of this can be found at:
> https://medium.com/@nusenu/who-controls-tors-dns-traffic-a74a7632e8ca
> 
> thanks for helping with DNS decentralization on the tor network,
> nusenu
> 
> 
> 
> _______________________________________________
> tor-relays mailing list
> tor-relays at lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 

-- 
Frënn vun der Ënn A.S.B.L. (NGO)
e. virii at enn.lu (GPG: 0xce8c12f32a2cf11b)
t. +352-27-40-20-30-4
w. https://enn.lu/