Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T14:35:44Zhttps://gitlab.torproject.org/legacy/trac/-/issues/11600Strange nameserver fail warning in Tor log2020-06-13T14:35:44Zs7rStrange nameserver fail warning in Tor logI am running an exit relay on Linux, my Tor version is 0.2.4.21
I checked the log and found this strange warnings:
Apr 24 15:14:07.000 [notice] Circuit handshake stats since last time: 91698/91698 TAP, 15988/15988 NTor.
Apr 24 17:40:45....I am running an exit relay on Linux, my Tor version is 0.2.4.21
I checked the log and found this strange warnings:
Apr 24 15:14:07.000 [notice] Circuit handshake stats since last time: 91698/91698 TAP, 15988/15988 NTor.
Apr 24 17:40:45.000 [warn] eventdns: All nameservers have failed
Apr 24 17:40:45.000 [notice] eventdns: Nameserver <ISP-resolver1>:53 is back up
Apr 24 18:01:51.000 [warn] eventdns: All nameservers have failed
Apr 24 18:01:51.000 [notice] eventdns: Nameserver <ISP-resolver2>:53 is back up
Apr 24 18:01:52.000 [warn] eventdns: All nameservers have failed
Apr 24 18:01:53.000 [notice] eventdns: Nameserver <ISP-resolver1>:53 is back up
Apr 24 18:02:00.000 [warn] eventdns: All nameservers have failed
Apr 24 18:02:01.000 [notice] eventdns: Nameserver <ISP-resolver1>:53 is back up
Apr 24 18:02:01.000 [warn] eventdns: All nameservers have failed
Apr 24 18:02:01.000 [notice] eventdns: Nameserver <ISP-resolver2>:53 is back up
Apr 24 19:46:22.000 [warn] eventdns: All nameservers have failed
Apr 24 19:46:22.000 [notice] eventdns: Nameserver <ISP-resolver2>:53 is back up
Apr 24 20:46:25.000 [warn] eventdns: All nameservers have failed
Apr 24 20:46:25.000 [notice] eventdns: Nameserver <ISP-resolver2>:53 is back up
Apr 24 21:14:07.000 [notice] Heartbeat: Tor's uptime is 8 days 12:00 hours, with 13940 circuits open. I've sent 549.49 GB and received 543.20 GB.
So I thought it's the fault of the nameservers provided by the ISP. Fair enough, I have configured my own resolver on localhost (where the relay is running) using BIND 9.10 (latest stable) with dnssec-validation and everything. I thought I fixed it. After some time, I checked the logs again and:
Apr 24 23:26:03.000 [warn] eventdns: All nameservers have failed
Apr 24 23:26:03.000 [notice] eventdns: Nameserver 127.0.0.1:53 is back up
Apr 25 02:04:02.000 [warn] eventdns: All nameservers have failed
Apr 25 02:04:02.000 [notice] eventdns: Nameserver 127.0.0.1:53 is back up
Apr 25 02:04:03.000 [warn] eventdns: All nameservers have failed
Apr 25 02:04:04.000 [notice] eventdns: Nameserver 127.0.0.1:53 is back up
Apr 25 02:04:04.000 [warn] eventdns: All nameservers have failed
Apr 25 02:04:05.000 [notice] eventdns: Nameserver 127.0.0.1:53 is back up
Apr 25 02:04:06.000 [warn] eventdns: All nameservers have failed
Apr 25 02:04:06.000 [notice] eventdns: Nameserver 127.0.0.1:53 is back up
Apr 25 02:04:08.000 [warn] eventdns: All nameservers have failed
Apr 25 02:04:08.000 [notice] eventdns: Nameserver 127.0.0.1:53 is back up
Looks like its something Tor related. Why do I get this warning? Does this have any penalty on the performance or over the users who are using this node as an exit point? Should I just leave it alone as it works fine? From what I see nameservers fail and get back online immediately, fail and back on have same timestamp. Advices? Thanks in advance.Tor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/5932eventdns rejecting adresses2020-06-13T14:19:44ZTraceventdns rejecting adressesOn a Tor exit node, I saw this message in the logs :
[WARN] eventdns rejected address [scrubbed].
I don't have more information, but Sebastian pointed out that it indicates there was a problem somewhere with a DNS query, likely a bug ...On a Tor exit node, I saw this message in the logs :
[WARN] eventdns rejected address [scrubbed].
I don't have more information, but Sebastian pointed out that it indicates there was a problem somewhere with a DNS query, likely a bug in Tor.
Because of the lack of details in the message and logs, I don't know how to reproduce this bug.
**Trac**:
**Username**: koolfyTor: 0.2.3.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/3056surprising dns responses received from hosts that aren't our resolver2020-06-13T14:10:16ZTracsurprising dns responses received from hosts that aren't our resolverThis is my first ticket, so bear with me pls. On IRC "Sebastian" asked me to file a bug report
I'm using tor 2.2.25-alpha, vidalia 0.2.12
debian squeeze/wheezy, Linux kernel 2.6.38-2-686
I run a relay and allow all exit policies normal...This is my first ticket, so bear with me pls. On IRC "Sebastian" asked me to file a bug report
I'm using tor 2.2.25-alpha, vidalia 0.2.12
debian squeeze/wheezy, Linux kernel 2.6.38-2-686
I run a relay and allow all exit policies normally.
Run from residential cable modem, timewarner/brighthouse/roadrunner.
iptables and guarddog firewall with many recommended ports open.
this is my torrc:
# This file was generated by Tor; if you edit it, comments will not be preserved
# The old torrc file was renamed to torrc.orig.1 or similar, and Tor will ignore it
ContactInfo xxx
ControlPort 9051
DirPort 9030
HashedControlPassword 16:C87CFFBB8A7A0E6C60762C632961A38C9528FF12E165B8D691F55BE104
Log notice stdout
Nickname freeeveryone4ever
ORPort 9001
RelayBandwidthBurst 393216
RelayBandwidthRate 196608
my error msgs:
"eventdns: Address mismatch on received DNS packet. Apparent source was 10.10.7.2xx:5300"
I also get this msg every 10-30 mins: "[Warning] eventdns: All nameservers have failed" they come backup within a min or 2
also get this, for what it's worth:
"DNS Hijacking Detected - Tor detected that your DNS provider is providing false responses for domains that do not exist. Some ISPs and other DNS providers, such as OpenDNS, are known to do this in order to display their own search or advertising pages."
Tor seems to keep working, I just thought you'd want to know about these messages.
Thanks, freeeveryone4ever (also my relay name)
ps. let me know if you need more info.
**Trac**:
**Username**: freeeveryone4everTor: 0.3.2.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/legacy/trac/-/issues/1936"All nameservers have failed" eventdns message2020-06-13T14:06:33ZTrac"All nameservers have failed" eventdns messageThe symptom is messages appearing in the log after some uptime, usually several days:
Sep 11 10:42:30.665 [warn] eventdns: All nameservers have failed
Sep 11 10:42:39.684 [notice] eventdns: Nameserver 4.2.2.1 is back up
Sep 13 08:56:58....The symptom is messages appearing in the log after some uptime, usually several days:
Sep 11 10:42:30.665 [warn] eventdns: All nameservers have failed
Sep 11 10:42:39.684 [notice] eventdns: Nameserver 4.2.2.1 is back up
Sep 13 08:56:58.089 [warn] eventdns: All nameservers have failed
Sep 13 08:57:01.788 [notice] eventdns: Nameserver 4.2.2.1 is back up
Sep 13 08:57:03.089 [warn] eventdns: All nameservers have failed
Sep 13 08:57:12.396 [notice] eventdns: Nameserver 4.2.2.2 is back up
After that tor process usually terminates without warning.
There are numerous reports about this issue on the net, just if you try to google that log message.
**Trac**:
**Username**: varnavTor: unspecified