Skip to content
Snippets Groups Projects

"All nameservers have failed" eventdns message

    • Closed (moved) Issue created by Trac @tracbot

    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: varnav

    To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information

    Child items ...

    • Activity

    • Trac changed milestone to %Tor: unspecified

      changed milestone to %Tor: unspecified

    • Trac added component::core tor/tor eventdns milestone::Tor: unspecified priority::medium reporter::varnav resolution::worksforme severity::normal status::closed tor-relay type::defect version::tor 0.2.3.10-alpha labels

      added component::core tor/tor eventdns milestone::Tor: unspecified priority::medium reporter::varnav resolution::worksforme severity::normal status::closed tor-relay type::defect version::tor 0.2.3.10-alpha labels

    • Nick Mathewson
      Nick Mathewson @nickm ·

      This happens less with more recent eventdns versions, as included with recent 0.2.2.x-alpha versions, though I don't know whether we've got it completely solved in 0.2.2.x or not. I'm putting this one in "unspecified"; if it recurs with recent 0.2.2.x (or worse, with 02.3.x using Libevent 2.0.9's eventdns code) and we can track down what's going on, we should up the priority, call it a libevent bug, or both.

      Trac:
      Milestone: N/A to Tor: unspecified

    • Roger Dingledine
      Roger Dingledine @arma ·

      Replying to varnav:

      After that tor process usually terminates without warning.

      I don't know of any crash or assert bugs associated with these log messages. My guess is that's something different.

      Does it still happen on Tor 0.2.1.27?

    • C
      cypherpunks @cypherpunks ·

      HI,

      Running Tor v0.2.1.30. I got the same problem today. Warning eventdns: All nameservers have failed Warning eventdns: Nameserver 198.168.0.1is backup.

      Tor works fine for me.

      Trac:
      Actualpoints: N/A to N/A
      Points: N/A to N/A

    • Trac
      Trac @tracbot ·
      Author

      Whats Up Varnav. I too get the Warning eventdns: All nameservers have failed and my network is running fine but I managed to pinpoint the problem to a few things. It's either an overload of the system. My router is cross connecting and can't handle the load, one of my network files is configure wrong or my ISP is kicking me off do to the increase of traffic to their network. Don't know yet? These are just my theories. I don't know what operating system you are running on but I'm on Ubuntu 10.10. Linux version 2.6.35-28-generic I'm also running the latest Tor Bundle for Linux. Anyways, here is the link I used to get an idea of what my network is doing.
      http://www.linuxhomenetworking.com/wiki/index.php/Quick_HOWTO_:Ch04:_Simple_Network_Troubleshooting Hope it helps. Once I solved this problem I will post it. Peace out Pem10777

      Trac:
      Username: pem10777
      Summary: "All nameservers have failed" eventdns message to Warning eventdns: All nameservers have failed
      Version: Tor: 0.2.1.26 to Tor: unspecified
      Keywords: N/A deleted, Warning eventdns: All nameservers have failed added
      Milestone: Tor: unspecified to Tor Browser Bundle for Linux

    • Nick Mathewson
      Nick Mathewson @nickm ·

      Trac:
      Milestone: Tor Browser Bundle for Linux to Tor: unspecified
      Keywords: Warning eventdns: All nameservers have failed deleted, eventdns added

    • R
      Robert Ransom @rransom ·

      Trac:
      Summary: Warning eventdns: All nameservers have failed to "All nameservers have failed" eventdns message
      Version: Tor: unspecified to Tor: 0.2.1.26

    • Trac
      Trac @tracbot ·
      Author

      What up Varnav. Still working on this problem and getting a bit closer every day. Here is a tool that you might find helpful. Go to the bottom of this site http://www.atagar.com/arm/ download it and run it. It will ask you for a password. Its the password you set up when you started your relay. If you are running vidalia go to settings advanced section and un-click the Randomly Generate. Authentication should be set to password and then make up your password. Click ok and you are done. Go to terminal type in arm and then the password and you are money.

      Trac:
      Username: pem10777

    • Trac
      Trac @tracbot ·
      Author

      I am seeing these annoying messages too. They come up every 1-2 minutes and are filling up my logs.

      I am running the latest dev version on Debian Squeeze. Binaries are self compiled with libevent 2.0 and openssl 1.0.0. As local DNS cache is ubound running which forwards DNS to google public DNS. ubound is configured with 16 threads. I don't think that DNS is screwed up in my case.

      Trac:
      Username: torland
      Version: Tor: 0.2.1.26 to Tor: 0.2.3.10-alpha

    • Trac
      Trac @tracbot ·
      Author

      One more thing: the message comes always as

      13:10:25 [WARN] eventdns: All nameservers have failed 13:10:25 [NOTICE] eventdns: Nameserver 127.0.0.1:53 is back up

      between the failure and recover are only a couple of milliseconds

      Trac:
      Username: torland

    • Nick Mathewson
      Nick Mathewson @nickm ·

      Trac:
      Keywords: eventdns deleted, eventdns tor-relay added

    • Nick Mathewson
      Nick Mathewson @nickm ·

      Trac:
      Component: Tor Relay to Tor

    • Trac
      Trac @tracbot ·
      Author

      I've encountered this bug, but I've "resolved" it by changing DNS. On Linux it is /etc/resolv.conf but in my case I installed my own DNS "cache" using DJBDNS http://cr.yp.to/djbdns.html

      The message has since disappeared from the logs. If others can confirm, I guess this could be perhaps pointed at in the FAQs...?

      I think it happens when your DNS is either:

      • too slow (if you're using a home router that can't keep up), or
      • has some form of rate-limiting

      Trac:
      Username: alt255
      Cc: N/A to alt255

    • Trac
      Trac @tracbot ·
      Author

      The issue could be as described above or alternately could be the result of malformed DNS requests as described in bug #11600 (moved) comment 6.

      Trac:
      Username: hdqdak8v32aor
      Sponsor: N/A to N/A
      Severity: N/A to Normal
      Reviewer: N/A to N/A

    • Nick Mathewson
      Nick Mathewson @nickm ·

      We've done a lot of work to clean this up over the years; whatever's going on here, it is different now than it was 3 years ago.

      Trac:
      Status: new to closed
      Resolution: N/A to worksforme

    • Trac closed

      closed

    • Nick Mathewson mentioned in issue #11600 (moved)

      mentioned in issue #11600 (moved)

    • Trac moved to tpo/core/tor#1936 (closed)

      moved to tpo/core/tor#1936 (closed)

    Please register or sign in to reply