Comments

19 comments

  • Official comment
    Avatar
    Reg Ham

    What is the ddclient that you are using when you receive this error. 

    Is it DNS-O-Matic or something else. 

    In addition, there are a few characters that cannot be used in passwords used in the Dynamic IP Updater Client. These characters include:***^, &, , ~, `,*** and ***%***. Please change your OpenDNS account password so you don't include any of non-alphanumeric characters: https://dashboard.opendns.com/myaccount/password

    In addition, please also check to make sure that the system time and time zone are correct on your computer.

     

    Comment actions Permalink
  • Avatar
    cedjo

    when you change your password you are requested to provide a password with non-alphanumeric characters...

    I have also a badauth since 1 day from synology NAS, postman request, manual tests or ddclient.

    I have changed password but nothing is working.

    0
    Comment actions Permalink
  • Avatar
    openme12

    Same here. Changed nothing on my end, and now overnight get bad authentication on both Synology NAS and Asus router all of a sudden.

    My original password had one special character (a dot), tried to change it to one just alfanumeric, but OpenDNS needs a special character in password, so put in a dash. Stil getting the error.

    0
    Comment actions Permalink
  • Avatar
    flash13

    I'm having the same behavior, seems something with their authentication system.  I saw the behavior with my (legacy) Synology DDNS alerting starting yesterday.  I have tried updating via a couple of dnsomatic containers in Docker and using the DirectUpdate application.  Each one returns "badauth" when it is the same credentials I have used for a couple of years and successfully logged into this forum with.  

    Hate to say it, but it's you (opendns/dnsomatic), not me.  At least this time.

    0
    Comment actions Permalink
  • Avatar
    Reg Ham

    In general, if DNS-O-Matic is handing back a `badauth` error, this means that the username and/or password that are being passed to its API are incorrect.

    There are a few characters that cannot be used in passwords used in the Dynamic IP Updater Client. These characters include:***^, &, , ~, `,*** and ***%***. Please change your OpenDNS account password so you don't include any of non-alphanumeric characters: https://dashboard.opendns.com/myaccount/password

    In addition, please also check to make sure that the system time and time zone are correct on your computer.

    Please try using this link to reset your password https://www.dnsomatic.com/account/ 

     

    In addition 

     

    If this does not help please try the following URL:

    https://updates.dnsomatic.com/nic/update?hostname=Home

    0
    Comment actions Permalink
  • Avatar
    stephanvs

    Same here with a mikrotik router. When accessing the link from Edge, it asks for username (email) and password (update-only password), but then nothing happens, it asks again and again...

    0
    Comment actions Permalink
  • Avatar
    cedjo

    I did reset my password, with only $ in it, same problem.

    still not working

    0
    Comment actions Permalink
  • Avatar
    Reg Ham

    If the steps above do not resolve the problem I would suggest that you create a support request so we can further troubleshoot the problem

    0
    Comment actions Permalink
  • Avatar
    cedjo

    Hi Reg,

    this is already done:

    ticket number is [892687]

    https://support.opendns.com/hc/requests/892687

    Regards

     

    0
    Comment actions Permalink
  • Avatar
    anstelioss (Edited )

    Same issue here.

    Changed nothing and getting badauth from https://updates.opendns.com/nic/update? on my Synology NAS since 4-5 days ago.

    0
    Comment actions Permalink
  • Avatar
    nesdns (Edited )

    Reg Ham I have this issue too, it started yesterday.

    Prior to this my Synology router was updating my DNS-o-Matic account without issue. I've a custom DDNS update in DSM 7's Control Panel (Synology NAS) that was a fallback for if the router was replaced, this custom DDNS was working but now isn't too.

    Also, on Mac, dDNS Broker cannot access DNS-o-Matic not OpenDNS accounts to update them. Plus using Mac's Terminal and 'curl' with a correctly crafted URL (with username/password, using HTML character code %40 for @) doesn't work, nor does using Safari with the correctly crafted URL (without username/password): where the authentication just repeats itself.

    Using 'curl' returns 'badauth' yet I can log into DNS-o-Matic and OpenDNS web sites, as evidenced by being able to post here.

    I've tried updating my account password and that had no effect.

    I've raised a support ticket (#893086) and referenced this community thread.

    0
    Comment actions Permalink
  • Avatar
    robertot

    Same issue here, I noticed it today.

    I tried using "ddclient" instead of "inadyn" (under Debian Linux) but the result did not change.

    Opened support ticket #893303.

    0
    Comment actions Permalink
  • Avatar
    vagabondb

    I started having the same issue with curl command in my update script. I noticed the issue firstly appeared on the 7th of December. Before then everything worked well. At least what can I see from logs

    0
    Comment actions Permalink
  • Avatar
    robertot (Edited )

    It works again.

    0
    Comment actions Permalink
  • Avatar
    vagabondb

    Thanks, indeed. Probably they have fixed something.

    0
    Comment actions Permalink
  • Avatar
    nesdns

    Thanks all for posting that it has started to work again. Only having issues with dDNS Broker on Mac (looks from the Mc App Store) that the developer has moved onto a new version with subscription payment. Oh well, I've a fallback script for my DDNS services, plus the primary service in Synology SRM now works.

    If anyone is looking for a custom provider query URL to be added in Synology DSM 7's Control Panel, I find that this works:

    https://updates.dnsomatic.com/nic/update?hostname=__HOSTNAME__&myip=__MYIP__&wildcard=NOCHG&mx=NOCHG&backmx=NOCHG

    0
    Comment actions Permalink
  • Avatar
    flash13

    Working for me again as well, thanks to everyone that posted here having issues.

    I would really like to know what the issue was on their end so when it happens again we can collectively point to that for them to investigate.

    Thanks!

    0
    Comment actions Permalink
  • Avatar
    openme12

    Yep, working for me again too...glad it got solved, thanks all for posting

    0
    Comment actions Permalink
  • Avatar
    Reg Ham

    Glad to hear that the problem has been resolved for most of you.

    0
    Comment actions Permalink

Please sign in to leave a comment.