Results 1 to 10 of 10
  1. #1
    Master Untangler
    Join Date
    Dec 2018
    Posts
    165

    Default DNS-O-Matic DDNS update failing

    I know that my login/password is correct so I am at a loss.

    All I can get from ddclient is a 401 Unauthorized error. If I take the credentials from the ddclient.conf file and plug them in at the website I log right in.

    I tried using all.dnsomatic.com for the hostname as well.

    Any thoughts would be appreciated.

  2. #2
    Untangler jcoffin's Avatar
    Join Date
    Aug 2008
    Location
    Sunnyvale, CA
    Posts
    8,522

    Default

    Quote Originally Posted by jlficken View Post
    I know that my login/password is correct so I am at a loss.

    All I can get from ddclient is a 401 Unauthorized error. If I take the credentials from the ddclient.conf file and plug them in at the website I log right in.
    I tried using all.dnsomatic.com for the hostname as well.
    The hostname field in the service configuration has to match the one set for your account.
    Attention: Support and help on the Untangle Forums is provided by
    volunteers and community members like yourself.
    If you need Untangle support please call or email support@untangle.com

  3. #3
    Master Untangler
    Join Date
    Dec 2018
    Posts
    165

    Default

    I have tried using my actual domain as well as the all.dnsomatic.com since that was suggested on their website as well as in an old thread on here.

    Here is my current ddclient.conf (sanitized):
    pid=/var/run/ddclient.pid
    use=web web=myip.dnsomatic.com/
    protocol=dyndns2
    login=<login>
    password=<password>
    ssl=yes
    server=updates.dnsomatic.com
    <my domain>.info

    Here is the result of the last update attempt from syslog:
    Jan 9 08:39:25 5018D-FN8T ddclient[10600]: FAILED: updating <my domain>.info: authorization failed (HTTP/1.0 401 Unauthorized
    Jan 9 08:39:25 5018D-FN8T ddclient[10600]: FAILED: date: Thu, 09 Jan 2020 14:39:24 GMT
    Jan 9 08:39:25 5018D-FN8T ddclient[10600]: FAILED: server: opendns
    Jan 9 08:39:25 5018D-FN8T ddclient[10600]: FAILED: www-authenticate: Basic realm="DNSOMATIC"
    Jan 9 08:39:25 5018D-FN8T ddclient[10600]: FAILED: content-length: 7
    Jan 9 08:39:25 5018D-FN8T ddclient[10600]: FAILED: content-type: text/html; charset=UTF-8
    Jan 9 08:39:25 5018D-FN8T ddclient[10600]: FAILED: x-xss-protection: 1; mode=block
    Jan 9 08:39:25 5018D-FN8T ddclient[10600]: FAILED: x-ingress-point: dfw
    Jan 9 08:39:25 5018D-FN8T ddclient[10600]: FAILED: connection: close
    Jan 9 08:39:25 5018D-FN8T ddclient[10600]: FAILED:
    Jan 9 08:39:25 5018D-FN8T ddclient[10600]: FAILED: badauth)

  4. #4
    Master Untangler
    Join Date
    Dec 2018
    Posts
    165

    Default

    This is the old thread that I was referencing - https://forums.untangle.com/networki...s-v14-1-a.html

    Also, a CloudFlare article on DNS-O-Matic that I tried - https://support.cloudflare.com/hc/en...s/360020524512

  5. #5
    Master Untangler
    Join Date
    Dec 2018
    Posts
    165

    Default

    Here is the ddclient config help page from DNS-O-Matic - https://www.dnsomatic.com/wiki/ddclient

  6. #6
    Master Untangler TirsoJRP's Avatar
    Join Date
    Oct 2010
    Posts
    409

    Default

    Be aware that manual settings to the ddclient.conf file will get lost on reboot and config changes.

  7. #7
    Master Untangler
    Join Date
    Dec 2018
    Posts
    165

    Default

    Quote Originally Posted by TirsoJRP View Post
    Be aware that manual settings to the ddclient.conf file will get lost on reboot and config changes.
    Thanks for the warning!

    I was just modifying it to test but nothing seems to work. I may just have to stick with the UnRAID docker to update Cloudflare directly since it works fine. I just wanted to stick to using the router if possible.

    I wish that Cloudflare could be added back into Untangle as it is by far the best option out there.

  8. #8
    Master Untangler
    Join Date
    Dec 2018
    Posts
    165

    Default

    I finally got it working!!!!

    DNS-O-Matic Cloudflare service settings:
    Email - <duh>
    API Token - <Global API Token from Cloudflare>
    Hostname - <your reference for updating>
    Domain - <your domain name>

    Untangle:
    Service - DNS-O-Matic
    Username - <DNS-O-Matic User Name>

    Password - <DNS-O-Matic Password> NOTE: The password CANNOT contain an =, ?, or & or else you will get 401 Unauthorized errors from ddclient!! I wound up using a password with a single ! and the rest being numbers/letters and it then worked correctly.

    Hostname(s) - <The value entered in the Hostname field of DNS-O-Matic> Note: You can also use all.dnsomatic.com to assign the current IP to all of your services.
    Last edited by jlficken; 01-09-2020 at 12:34 PM.

  9. #9
    Untangler jcoffin's Avatar
    Join Date
    Aug 2008
    Location
    Sunnyvale, CA
    Posts
    8,522

    Default

    Awesome. Thanks for posting the solution.
    Attention: Support and help on the Untangle Forums is provided by
    volunteers and community members like yourself.
    If you need Untangle support please call or email support@untangle.com

  10. #10
    Master Untangler
    Join Date
    Dec 2018
    Posts
    165

    Default

    Quote Originally Posted by jcoffin View Post
    Awesome. Thanks for posting the solution.
    No problem. I edited it a bit to clarify a couple of things and add some Hostname field info.

    Now I'm happy again as this has been driving me insane for 4 or 5 hours now

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

SEO by vBSEO 3.6.0 PL2