<html><head></head><body>Great thread! I just use the recommended onces that support dnssec<br><br><div class="gmail_quote">On May 11, 2018 11:55:39 AM UTC, tor-relays-request@lists.torproject.org wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">Send tor-relays mailing list submissions to<br> tor-relays@lists.torproject.org<br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays<br>or, via email, send a message with subject or body 'help' to<br> tor-relays-request@lists.torproject.org<br><br>You can reach the person managing the list at<br> tor-relays-owner@lists.torproject.org<br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of tor-relays digest..."<br><br><br>Today's Topics:<br><br> 1. lets stop using central big DNS resolvers (Google, Level3,<br> OpenDNS, Quad9, Cloudflare) (nusenu)<br> 2. Re: lets stop using central big DNS resolvers (Google,<br> Level3, OpenDNS, Quad9, Cloudflare) (Tyler Durden)<br> 3. Re: lets stop using central big DNS resolvers (Google,<br> Level3, OpenDNS, Quad9, Cloudflare) (nusenu)<br> 4. PSA regarding Quad9 DNS Resolver (Nathaniel Suchy (Lunorian))<br> 5. Re: Strange BGP activity with my node (Johan Nilsson)<br> 6. Re: lets stop using central big DNS resolvers (Google,<br> Level3, OpenDNS, Quad9, Cloudflare) (Nathaniel Suchy (Lunorian))<br><br><br><hr><br><br>Message: 1<br>Date: Thu, 10 May 2018 22:16:00 +0000<br>From: nusenu <nusenu-lists@riseup.net><br>To: tor-relays@lists.torproject.org<br>Subject: [tor-relays] lets stop using central big DNS resolvers<br> (Google, Level3, OpenDNS, Quad9, Cloudflare)<br>Message-ID: <5e7d99ef-9514-cee4-985f-7f1d4a21dfec@riseup.net><br>Content-Type: text/plain; charset="utf-8"<br><br>Dear Exit Relay Operators,<br><br>I'd like to invite you to check your exit's DNS resolver by <br>having a look at the following list of exits using resolvers<br>outside their AS (especially if it is Google, OpenDNS, Quad9 or Cloudflare).<br><br>You can search the list for you contactinfo, relay nickname or relay fingerprint (first 8 characters):<br><br><a href="https://gist.github.com/nusenu/cb766ff7945fafd9f90ee7f211a2508f#file-tor-dns-april-2018-txt">https://gist.github.com/nusenu/cb766ff7945fafd9f90ee7f211a2508f#file-tor-dns-april-2018-txt</a><br><br><br>I extended the "DNS on Exit Relays" section in the Tor Relay Guide<br>to include specific instructions what is recommended for Tor exit operators with <br>regards to DNS on exit relays.<br><br><a href="https://trac.torproject.org/projects/tor/wiki/TorRelayGuide#DNSonExitRelays">https://trac.torproject.org/projects/tor/wiki/TorRelayGuide#DNSonExitRelays</a><br><br>If you found yourself on the list above and changed your DNS to a local (same host or same AS)<br>resolver or found a false-positive, please drop me an email (off-list is also ok).<br><br><br>The goal is to be bellow the following thresholds within one year:<br>- not have any single remoteAS entity control more than 10% exit capacity<br>- reduce the overall remoteAS share to bellow 20% exit capacity<br><br>the longer version of this can be found at:<br><a href="https://medium.com/@nusenu/who-controls-tors-dns-traffic-a74a7632e8ca">https://medium.com/@nusenu/who-controls-tors-dns-traffic-a74a7632e8ca</a><br><br>thanks for helping with DNS decentralization on the tor network,<br>nusenu<br></pre></blockquote></div><br>
-- <br>
Take Care Sincerely flipchan layerprox dev</body></html>