On Sep 7, 2013, at 20:55 , Peter Palfrader wrote: > Running a local bind or unbound is probably a smart thing to do, and if > you put 127.0.0.1 into /etc/resolv.conf tor will use that. I now have a local Bind9 running, but I still get a lot of these: Sep 08 22:11:27.000 [warn] eventdns: All nameservers have failed Sep 08 22:11:27.000 [notice] eventdns: Nameserver 127.0.0.1:53 is back up Sep 08 22:15:39.000 [warn] eventdns: All nameservers have failed Sep 08 22:15:39.000 [notice] eventdns: Nameserver 127.0.0.1:53 is back up Sep 08 22:16:46.000 [warn] eventdns: All nameservers have failed Sep 08 22:16:46.000 [notice] eventdns: Nameserver 127.0.0.1:53 is back up The /var/log/syslog contains a lot of these, but timestamps don't match with the outages reported by Tor (hostnames and IP addresses changed): Sep 8 22:13:59 tor-exit named[11467]: lame server resolving 'www.example.hk' (in 'example.hk'?): 123.123.123.123#53 Sep 8 22:14:17 tor-exit named[11467]: error (connection refused) resolving 'www.example.com/A/IN': 123.123.123.123#53 Sep 8 22:14:18 tor-exit named[11467]: validating @0x123456789abc: www.example.com A: no valid signature found Sep 8 22:14:32 tor-exit named[11467]: error (unexpected RCODE REFUSED) resolving 'www.example.de/A/IN': 123.123.123.123#53 Any suggestions? // Yoriz
Attachment:
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ tor-relays mailing list tor-relays@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays