Suddenly odd emails from opendns with message !yours - no kidding

Comments

10 comments

  • Avatar
    bowlby4

    I received the same error. The html ip they say i have and you have (67.215.93.179) is actually registered to OpenDNS. I think the problem is on their end. Hopefully it will be fixed soon. 

  • Avatar
    bowlby4

    Autocorrect changed http to html :(

  • Avatar
    parbulo

    i'm getting this same error, so i deleted the network and create a new one. i got this error :

    Network Verification

    Your IP (67.215.93.179) does not match the one you are trying to verify.

    thats not my ip.  my real ip starts with  181.53...

    and i'm not using any special connection or vpn, i'm on windows in secure mode with networking. and i get this message.

    also https://db-ip.com/all/67.215.93 says that direction "67.215.93.179" allows to open dns services, and not me or any external connection.

    when i visit https://ipinfo.io/ or any site to see my ip i always see my 181.53.

    so , guys what cand i do?

     

     

  • Avatar
    glnz
    Everyone - open a support ticket at https://support.opendns.com/requests/new so we let them know something is wrong.
  • Avatar
    mattwilson9090

    Deleting your network is almost always counterproductive, and in this case it guarantees that you won't have any OpenDNS service until they resolve whatever changed on their backend. Please, no one delete your network as part of your troubleshooting process unless you've exhausted all possibilities, including posting questions here in this forum and opening a support ticket with OpenDNS. The only times I've seen deleting a network be of any use is if an existing network is associated with an OpenDNS account type that either no longer exists, or where the subscription has expired or not be renewed. It's not going to be of any use to you if you are using OpenDNS Home.

    Whatever happened, something changed at OpenDNS that is preventing registration of new networks or updating addresses because something at OpenDNS is improperly detecting the address where the requests are coming from. Until they resolve that it doesn't appear as if anyone is going to be able to create a new network or update an address. On the plus side, OpenDNS is still providing recursive DNS service, and for those whose registered address is still valid it will continue filtering.

    However, please, everyone let's NOT all open a ticket. That will only flood their engineers and staff with redundant tickets that will have to be resolved individually and manually. If they don't know about this issue already they'll know about it the first time they open a related ticket. Having hundreds of tickets behind it in the queue for the same issue won't speed up resolving that first ticket  or the problem itself, it will only slow down resolving issues not related to this.

  • Avatar
    glnz
    Matt - sorry for suggesting the wrong thing. FYI, my network is "Inactive" on my Open DNS Dashboard. I assume that's part of the problem they're having.
  • Avatar
    mattwilson9090

    @glnz I'm not sure that the "inactive" portion of it has anything to do with this, but the symptoms you described in your initial post are the same as others are reporting and what I've observed on my own account.

    Is the address currently registered for your network your actual IP address, or is it an old one? The "inactive" message may be related to some other issue that you are also experiencing.

    Have you opened a support ticket yourself? You seem to have been the first one to post about this in the forum, in fact I was troubleshooting this on my end when I saw your message.

  • Avatar
    rotblitz

    According to https://support.opendns.com/entries/101799428 the service has been restored.

  • Avatar
    glnz
    rotblitz and Daniel Cheung - you guys fixed it! Thanks. Happily " !yours ", glnz
  • Avatar
    rotblitz

    No, I definitely didn't fix this!  I'm just a user like you.  I only saw the Service Interruption announcement.  Staff like Daniel may have fixed it.

Please sign in to leave a comment.