roachfiend.com

  • firefox extensions
  • tutorials
  • faq
  • November 3, 2005

    BugMeNot.com is indeed down

    Filed under: general — Eric @ 6:33 pm

    Your Ad Here

    I don’t know why, or for how long, or anything. I sent the owner an e-mail, so hopefully I’ll find out why soon.

    So this means that the extension will not work, since it relies on the site for the information. We were planning on creating a contingency plan at some point, but obviously we fell short on that. Hopefully if it comes back up, we’ll create something for the future.

    *Edit: I just talked to the owner, and he said that it was a slight miscommunication with his domain provider, and it will be back up shortly. So keep your pants on- bugmenot.com shall rise again.*


    14 Responses to “BugMeNot.com is indeed down”

    1. mahk Says:

      crap

    2. dude Says:

      Taken down by the man. Bummer…

    3. bendotorg Says:

      Geez…it was working just a while ago. (like two hours ago).

    4. fhic Says:

      *Really* weird. Ten minutes ago it was down, but I’m doing a new Firefox install so I came here to get the extension. I installed it, and it worked! And now it’s down again. Funky.

    5. fhic Says:

      *Really* weird. Ten minutes ago it was down, but I’m doing a new Firefox install so I came here to get the extension. I installed it, and it worked! And now it’s down again. Funky.

      And now it’s up again! “No accounts found for roachfiend.com”

    6. Kevin Price Says:

      It looks like you can still get to BugMeNot directly at:
      http://bugmenot.nfshost.com

      I’m guessing that something messed up happened with domain name renewal.

    7. z101z Says:

      good

    8. David Kaspar Says:

      Is there at least any IP we can put in our host file meanwhile?

      Trying to tracert to bugmenot.nfshost.com causes problems at c2.phx.nearlyfreespeech.net [199.1.92.202].

    9. Foo Says:

      It’s working again. Indeed the domain renewal screwed up (yesterday you got godaddys “this domain is expired”-page).

      It appears to be fixed now
      Last Updated on: 03-Nov-05
      Domain servers in listed order:
      NS.PHX3.NEARLYFREESPEECH.NET
      NS.PHX5.NEARLYFREESPEECH.NET

      It were redirected to godaddys nameservers yesterday. If you’re using your ISPs nameservers the old records might be cached, so you’ll have to wait until the cache expires or use another nameserver.

    10. Eric Says:


      It was a domain issue, so it’s back up and kicking now.


    11. t Says:

      Is it not working again? :(

    12. Simon Geiser Says:

      real hot site love it

    13. dave Says:

      Blogging has definitely changed my life. I was amazed at how quickly the feeling of community came through. I’ve met some great “strangers” on line. I’ve learned from them and been encouraged by them.

    14. alan Says:

      Thanks for your helpful tips.

    Leave a Reply

    You must be logged in to post a comment.