DNS-O-MATIC is not updating? Status = Unknow. Got alot Errors

Comments

16 comments

  • Avatar
    scarbacks

    I might have figured it out. The problem occurs when you try to force DNS update to NO-IP and there is not really an IP change. For some reason, DNS-O-MATIC loses its connection with your NO-IP account and keep it as an 'unknown' status forever. The solution is to delete your NO-IP account from DNS-O-MATIC and set it up again. And do not force updates - make your router just update it when there is really an IP change.

    2
    Comment actions Permalink
  • Avatar
    Paul (Edited )

    I'm having the same issue with NO-IP updates.  I'm using a Synology router and updates were working OK until last week.  NO-IP support say that everything is OK their end and and updates via their own updater work fine.  I've checked my username and password and they're OK.

    1
    Comment actions Permalink
  • Avatar
    scarbacks (Edited )

    @linfidel I think the problem of forcing an DNS update is in the message received in DNS-O-MATIC. The e-mail says:

     

    No-IP response for '*************':
    --------------------

    --------------------

    I'm thinking: this blank response says that no update was made, because there was nothing to be updated. But DNS-O-MATIC can't recognize it. It put your NO-IP account in a 'unknown' state forever.

    I've made a few tests with my dd-wrt and I've noticed that when my public IP changes, the router automatically updates  DNS-O-MATIC, and DNS-O-MATIC Updates my NO-IP account. But if I force updates (like I was doing, once in a day) my dd-wrt is able to update DNS-O-MATIC, but it crashes NO-IP account by letting it in unknown state.

    If anyone here is having this same problem that I had. Try to do it: exclude your NO-IP account from DNS-O-MATIC and configure it again. Just let it be updated automatically. No foces. It will give DNS-O-MATIC an "OK" response and DNS-O-MATIC will keep working with your NO-IP account. It's worthy a try! ;-)

     

     

    As you can see... now my dd-wrt will only try to force update every 60 days (max value for dd-wrt routers). You don't actually need forced updates, because dd-wrt already updates it automatically when there is an IP change.

    1
    Comment actions Permalink
  • Avatar
    rotblitz (Edited )

    The most problematic part is your FRITZ!Box configuration.  Do not use "localhost" as domain name, but a real existing domain name which will be using your changing IP address, for example one of your no-IP hostnames, which one doesn't matter.  This domain name is being used to see if your IP address has changed, before an update is being made, and also after an update has been made to ensure that the update was successful.  The entry "localhost" cannot cover this.  You will already see a lot of related error messages in your router log.  And this causes also these many useless update trials with the error messages from DNS-O-Matic.

    So, fix this as first.  It probably already solves your problem.  If not, come back. 

    0
    Comment actions Permalink
  • Avatar
    DooMSandro

    rotblitz

    ok dude, but I use this now like more then 2-3 years with "localhost" and got NEVER a problem with it...

    I edit it now to my domain-name but still same problem

    "unknow" @ dns o matic and no ip response for..... (E-Mail is FULL of it! I got more then 200-300 E-Mails now...)

     

    Paul like my problem...same so!

     

    I thing DNS-O-Matic got some problems with his service and other stuff.

    I mean, why its works more then 2-3 years now with the same settings, and without changes, but not now?

    I did not change anythink on my server, Ports, DNS-O-Matic settings, NO-IP settings etc...

    0
    Comment actions Permalink
  • Avatar
    rotblitz

    If it is a problem with no-IP at DNS-O-Matic, then we other users here cannot help you. You must raise a support ticket, link “submit a request” above.

    0
    Comment actions Permalink
  • Avatar
    DooMSandro

    Ya mby...

     

    But i already send 2 request to the support but now answere till now...

    In this time, NO-IP send me like 3 replies already...so idk whats going on with the Support here :/

    0
    Comment actions Permalink
  • Avatar
    rotblitz (Edited )

    For this free service the SLA is up to 72 hours on business days, maybe more, depending on the number of tickets. It is now Saturday, not a business day.

    Also, I am a user like you and cannot stand in for OpenDNS.

    0
    Comment actions Permalink
  • Avatar
    DooMSandro

    Of course I am aware of this, but no feedback for 1 week?
    I didn't write to support today.
    NO-IP is also a free service and I was answered directly.


    Let's see what happens.

    0
    Comment actions Permalink
  • Avatar
    Permanently deleted user

    Any updates here. I’m also having the same problem.

    0
    Comment actions Permalink
  • Avatar
    linfidel (Edited )

    Are you trying to use SSL for the update?  If so, don't.

     

    EDIT:  This was an incorrect assumption on my part.  It seemed to fix the failure, but still did not actually work.  So, use SSL.

    0
    Comment actions Permalink
  • Avatar
    Permanently deleted user

    Nope, not using SSL.

    0
    Comment actions Permalink
  • Avatar
    chronocentric

    Having the same issue with No-IP and dnsomatic. I have my DD-WRT router setup to update dnsomatic, which then updates OpenDNS, No-IP and Google Domains. Everything updates fine except for No-IP. Status says "Unknown" and I get the same error email. I have contacted dnsomatic, no answer yet.

    0
    Comment actions Permalink
  • Avatar
    LeviandSandra

    Anyone ever get a resolution to this problem?

    0
    Comment actions Permalink
  • Avatar
    linfidel

    The solution to my problem may have nothing to do with any problems here, but I thought it might help to mention the solution for me.  I use Linux with ddclient software.  Since some routers use linux, it could conceivably affect them, too.

    I was getting an authorization error when I ran ddclient, which uses the script /etc/ddclient.conf.  The original source of this script was from the opendns web site at "https://support.opendns.com/hc/en-us/articles/227987727-Linux-IP-Updater-for-Dynamic-Networks).%C2%A0" (Linux IP Updater for Dynamic Networks).

    There was a subtle error in this script, and I had copied/pasted their script into my editor.  The error was the single quotes around the password.  These quotes were not the required single quotes, they were back quotes (or possibly only one was).  This was pretty hard to see, and took me a lot of debugging to find.  The difference is this - ` vs this - '.

    I finally was able to contact support and reported this to them (Mid March, 2020), so it has now been corrected.

     

    Note to rotblitz - please do not make any unhelpful comments.  You were wrong in your last one, saying this "free service", as some of us actually do pay for the VIP service.  I did, yet I still did not receive any answers from them until I reported the solution and outright told them their support sucked and I quit my VIP account because of this.

    To scarbacks - I don't think there is a problem forcing a DNS update, unless perhaps you do it too often.  For Linux, there can be a problem, which they document on the same page I referenced here, where a temporary file is created that must be deleted:  /var/cache/ddclient/ddclient.cache - but this is only for Linux.

     

    0
    Comment actions Permalink
  • Avatar
    rotblitz

    @linfidel
    I did not make unhelpful comments. I just said what the official statements are. And their support seems to be lousy lately, as many people report here.

    0
    Comment actions Permalink

Please sign in to leave a comment.