Opened 5 months ago

Last modified 3 months ago

#28860 new defect

Increased DNS failure rate when using ServerDNSResolvConfFile with tor (as opposed to 0.3.3.x)

Reported by: nusenu Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-dns, regression, 040-deferred-20190220
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


A major tor exit relay operator reports that
after upgrading from 0.3.3.x to his DNS failure rate significantly increased.

He also reported that he is observing DNS issues only when using ServerDNSResolvConfFile and no problems when not using that config option.
Using that option worked fine on tor 0.3.3.x

With ServerDNSResolvConfFile option on

Dec 13 02:39:52.000 [notice] eventdns: Nameserver is back up
Dec 13 02:39:53.000 [warn] eventdns: All nameservers have failed

Child Tickets

Change History (5)

comment:1 Changed 5 months ago by dgoulet

Keywords: tor-dns regression added
Milestone: Tor: 0.4.0.x-final

comment:2 Changed 5 months ago by arma


I don't know where to start here.

Is the person on the same version of libevent the whole time?

comment:3 Changed 5 months ago by nickm is google; it might be better on a relay not to use Google's DNS. I don't think that's the root problem here, though.

comment:4 Changed 5 months ago by arma

When you say 0.3.3.x, what is x?

For example I see that #21394 went in to

comment:5 Changed 3 months ago by nickm

Keywords: 040-deferred-20190220 added
Milestone: Tor: 0.4.0.x-finalTor: unspecified

Deferring 51 tickets from 0.4.0.x-final. Tagging them with 040-deferred-20190220 for visibility. These are the tickets that did not get 040-must, 040-can, or tor-ci.

Note: See TracTickets for help on using tickets.