Re: [tor-relays] exit operators: overall DNS failure rate above 5% - please check your DNS resolver

one of the underlying core issues is the lack of metrics data for relay operators. I filed the following feature requests to change this: provide DNS health metrics for tor exit relay operators https://trac.torproject.org/projects/tor/ticket/31290 non-public relay health metrics for operators

Re: [tor-relays] exit operators: overall DNS failure rate above 5% - please check your DNS resolver

Thanks for confirmation! That's what I was suspecting. Tim Niemeyer: > Moin > > I just played a bit with the sources of this test system. > > At first I didn't get it work, but then I changed the hard coded guard > to one of my own and voila .. > > > I picked an exit with an error rate of

Re: [tor-relays] exit operators: overall DNS failure rate above 5% - please check your DNS resolver

Moin I just played a bit with the sources of this test system. At first I didn't get it work, but then I changed the hard coded guard to one of my own and voila .. I picked an exit with an error rate of 100%: 0FF233C8D78A17B8DB7C8257D2E05CD5AA7C6B88 .. the test resultet in many many

Re: [tor-relays] exit operators: overall DNS failure rate above 5% - please check your DNS resolver

>> On Jun 30, 2019, at 8:32 PM, Matt Westfall wrote: >> >> Just set your exit relay DNS to 8.8.8.8 and 1.1.1.1 I mean dns traffic Screw that MITM. And unless your on box resolver lib runs nscd cache from rc when using remote dns above, busy exits can also save some bandwidth by running local

Re: [tor-relays] exit operators: overall DNS failure rate above 5% - please check your DNS resolver

Tim Niemeyer: > Maybe it is a load problem, because this machine has 100% cpu load? :( Generally speaking running a relay at 100% of hardware resources all the time will not make happy users and we should optimize for a smooth tor browser experience more than a high bw or hw resource usage. I

Re: [tor-relays] exit operators: overall DNS failure rate above 5% - please check your DNS resolver

> On 1 Jul 2019, at 21:41, Tyler Durden wrote: > > I can't really understand why our relays should fail so often because > the logs of our DNS daemon don't show anything and I haven't seen the > warning about nameservers that failed for a long time... > > Maybe the script that checks about DNS

Re: [tor-relays] exit operators: overall DNS failure rate above 5% - please check your DNS resolver

I can't really understand why our relays should fail so often because the logs of our DNS daemon don't show anything and I haven't seen the warning about nameservers that failed for a long time... Maybe the script that checks about DNS failures on Exits is not reporting correctly? Greetings

Re: [tor-relays] exit operators: overall DNS failure rate above 5% - please check your DNS resolver

On Sat, Jun 29, 2019 at 08:59:34AM +0200, Tim Niemeyer wrote: > There are 4 exits on one machine with one dns server. Only 3 of them > are shown in the list: > https://metrics.torproject.org/rs.html#search/as:AS205100 Looks like all four are listed, when I checked just now. > Maybe it is a load

Re: [tor-relays] exit operators: overall DNS failure rate above 5% - please check your DNS resolver

https://medium.com/@nusenu/who-controls-tors-dns-traffic-a74a7632e8ca ? > It would be neat for somebody (maybe somebody here?) to be tracking the > fraction of exit weights, over time, that are using these centralized > dns

Re: [tor-relays] exit operators: overall DNS failure rate above 5% - please check your DNS resolver

On Mon, Jul 01, 2019 at 10:06:08AM +0500, Roman Mamedov wrote: > On Mon, 01 Jul 2019 01:32:59 + > "Matt Westfall" wrote: > > > Just set your exit relay DNS to 8.8.8.8 and 1.1.1.1 I mean dns traffic > > isn't bulk traffic, let google and CloudFlare do the "work" > > It is considered to be a

Re: [tor-relays] exit operators: overall DNS failure rate above 5% - please check your DNS resolver

On Mon, 01 Jul 2019 01:32:59 + "Matt Westfall" wrote: > Just set your exit relay DNS to 8.8.8.8 and 1.1.1.1 I mean dns traffic > isn't bulk traffic, let google and CloudFlare do the "work" It is considered to be a bad idea privacy-wise:

Re: [tor-relays] exit operators: overall DNS failure rate above 5% - please check your DNS resolver

> On Jun 30, 2019, at 8:32 PM, Matt Westfall wrote: > > Just set your exit relay DNS to 8.8.8.8 and 1.1.1.1 I mean dns traffic isn't > bulk traffic, let google and CloudFlare do the “work" > Utilizing Google DNS (and possibly Cloudflare DNS) provides a significant security flaw that allows

Re: [tor-relays] exit operators: overall DNS failure rate above 5% - please check your DNS resolver

"Tim Niemeyer" To: tor-relays@lists.torproject.org Sent: 6/29/2019 2:59:34 AM Subject: Re: [tor-relays] exit operators: overall DNS failure rate above 5% - please check your DNS resolver Hi nusenu After reading your Mail, I realized that not the DNS records for the exit IPs are failing.

Re: [tor-relays] exit operators: overall DNS failure rate above 5% - please check your DNS resolver

Hi nusenu After reading your Mail, I realized that not the DNS records for the exit IPs are failing. Instead this list shows problems to resolve dns on the exit. I looked at our exit and all looks fine. Resolver works very fast and nothing imporint within the logfile. Only some dudes use

Re: [tor-relays] exit operators: overall DNS failure rate above 5% - please check your DNS resolver

Am 28.06.19 um 22:16 schrieb nusenu: > Dear Exit relay operators, > > first of all thanks for running exit relays! > > One of the crucial service that you provide in addition to forwarding > TCP streams is DNS resolution for tor clients. > Exit relays which fail to resolve hostnames > are barely

[tor-relays] exit operators: overall DNS failure rate above 5% - please check your DNS resolver

Dear Exit relay operators, first of all thanks for running exit relays! One of the crucial service that you provide in addition to forwarding TCP streams is DNS resolution for tor clients. Exit relays which fail to resolve hostnames are barely useful for tor clients. We noticed that lately