DNSOMATIC [401 Unauthorized] badauth
Recently DNSOmatic on my Asus RT-AX88U no longer works and system log shows [401 Unauthorized] badauth. I have checked settings and logged into OpenDNS and DNSomatic sites with my userid & password successfully, but appears to be an issue when connecting to : http://updates.dnsomatic.com/nic/update?hostname=all.dnsomatic.com which is hostname under setting required.
Have tried host name of updates.dnsomatic.com & all.dnsomatic.com with both userid & emai. This happened once OpenDNS became credential repository for DNSOMATIC and no response from OpenDNS support (crickets).
Thanks for insights and sharing experience/resolution if have one as I use to update Afraid.org DDNS.
Could you please advise for proper settings and troubleshooting?
System Log
Dec 7 15:41:11 start_ddns: Clear ddns cache.
Dec 7 15:41:11 start_ddns: update WWW.DNSOMATIC.COM default@dnsomatic.com, wan_unit 0
Dec 7 15:41:11 start_ddns: Start Inadyn.
Dec 7 15:41:11 inadyn[19230]: In-a-dyn version 2.8.1 -- Dynamic DNS update client.
Dec 7 15:41:11 inadyn[19230]: Update forced for alias updates.dnsomatic.com, new IP# 47.196.193.87
Dec 7 15:41:12 inadyn[19230]: Fatal error in DDNS server response:
Dec 7 15:41:12 inadyn[19230]: [401 Unauthorized] badauth
Dec 7 15:41:12 inadyn[19230]: Error response from DDNS server, exiting!
Dec 7 15:41:12 inadyn[19230]: Error code 50: Authentication failure
Dec 7 15:43:22 Mastiff: Got AAE_SIG_REMOTE_CONNECTION_TURNED_ON
Dec 7 15:43:22 rc_service: httpd 9292:notify_rc restart_ddns
-
I am also seeing the exact same badauth response since 06 Dec on RT-AX86U.
Also, my credentials cannot authenticate https://updates.dnsomatic.com/nic/update?hostname=all.dnsomatic.com\&myip=ipaddress&wildcard=NOCHG&mx=NOCHG&backmx=NOCHG. I can login without issues at dnsomatic/opendns.
-
Coincidentally, I was updating my script which updates the DNS around the same time. I was breaking my head over the last 4 days trying to debug why the auth was not working. http://updates.opendns.com/ endpoint is also giving badauth for me.
-
Getting the same. I have a cron job running that makes the HTTPS call using Curl. Started 7th Dec 2021 5:15am ADST. Was last successful at 5:10am. Using https://updates.opendns.com/nic/update?hostname={myhostname}
Does anyone from OpenDNS monitor this forum and able to provide insight into what is happening?
-
No chance to login to https://updates.opendns.com/nic/update at all even using browser. I think probably the free service is coming to the end of its life. :(
-
Facing the same issue since yesterday. Breaking my head against the wall, until checked more people are having the same problem.
Here are some logs that dnsomatic is indeed sending the IP address, problem occurs when ddclient tries to update opendns with acquired IP address. (Also used postman, and issue comes from updates.opendns.com request call)
DEBUG: proxy =
DEBUG: url = myip.dnsomatic.com
DEBUG: server = myip.dnsomatic.com
CONNECT: myip.dnsomatic.com
CONNECTED: using HTTP
SENDING: GET / HTTP/1.0
SENDING: Host: myip.dnsomatic.com
SENDING: User-Agent: ddclient/3.8.2
SENDING: Connection: close
SENDING:
RECEIVE: HTTP/1.1 200 OK
RECEIVE: Server: nginx
RECEIVE: Date: Fri, 10 Dec 2021 03:39:46 GMT
RECEIVE: Content-Type: text/plain; charset=utf-8
RECEIVE: Content-Length: 14
RECEIVE: Connection: close
RECEIVE: Strict-Transport-Security: max-age=2628000
RECEIVE: X-Frame-Options: deny
RECEIVE: X-XSS-Protection: 1; mode=block
RECEIVE:
RECEIVE: xxx.xxx.xxx.xx
DEBUG: get_ip: using web, myip.dnsomatic.com reports xxx.xxx.xxx.xx
DEBUG:
DEBUG: nic_dyndns2_update -------------------
INFO: setting IP address to xxx.xxx.xxx.xx for Home
UPDATE: updating Home
DEBUG: proxy =
DEBUG: url = http://updates.opendns.com/nic/update?system=dyndns&hostname=Home&myip=xxx.xxx.xxx.xx
DEBUG: server = updates.opendns.com
CONNECT: updates.opendns.com
CONNECTED: using HTTP
SENDING: GET /nic/update?system=dyndns&hostname=Home&myip=xxx.xxx.xxx.xx HTTP/1.0
SENDING: Host: updates.opendns.com
SENDING: Authorization: Basic xxx.xxx.xxx.xxxxx.xxx.xxx.xxxxx.xxx.xxx.xx
SENDING: User-Agent: ddclient/3.8.2
SENDING: Connection: close
SENDING:
RECEIVE: HTTP/1.0 200 OK
RECEIVE: date: Fri, 10 Dec 2021 03:39:48 GMT
RECEIVE: server: opendns
RECEIVE: vary: Accept-Encoding
RECEIVE: content-type: text/html; charset=UTF-8
RECEIVE: x-envoy-upstream-service-time: 10
RECEIVE: x-xss-protection: 1; mode=block
RECEIVE: x-ingress-point: lax
RECEIVE: connection: close
RECEIVE:
RECEIVE: badauth
FAILED: updating Home: badauth: Bad authorization (username or password) -
I was looking around, and I can see there was an incident service done 2 days ago, that might have affected us all
-
I received a response from support:
Are you still having this problem?
If so can you try updating your router/application to send updates to updates.dnsomatic.com using port 443 ( https://updates.dnsomatic.com )? We no longer allow updates to this service using port 80.
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
As well, please also check to make sure that the system time and time zone are correct on your computer.
My Response:
Thanks - I am still having the problem. My password does not included any of the characters you mention. I was already using port 443 (https://). A number of other folks are having the same issue and posting in the OpenDNS support forums: -
Ugh, just spent over an hour debugging this problem before leaving on a trip where I have to ensure I can access my home network! My password did have an $,%, and @ so I changed it and still not able to login. I tried other DNS clients and get the same message. I can't get OpenDNS or dns-o-matic to work. Same 401 errors as everyone else. Is the service dead?
-
Judging from the response of OpenDNS in the post of @... - i'd say there is a good chance too.
As well, please also check to make sure that the system time and time zone are correct on your computer.
Also this from their documentation page:
Users need to enter a DNS-O-Matic username and password. DNS-O-Matic usernames are 3-25 characters. DNS-O-Matic passwords are 6-20 characters. All ASCII letters and numbers accepted. Dots, dashes, and underscores allowed, but not at the beginning or end of the string.
-
tamadpoli
https://your_email:your_password@updates.dnsomatic.com/nic/update?hostname=all.dnsomatic.com&myip=xx.xx.xx.xx&wildcard=NOCHG&mx=NOCHG&backmx=NOCHG
replace the fields above with your creds and IP and paste in a browser
-
All, i experienced the same issue. It worked for me by passing the username and password NOT in the update url but outside
I mean, instead of using
curl -iRsSv --basic https://<username>:<password>@updates.dnsomatic.com/nic/update?hostname=
I used
curl -iRsSv --basic
https://<username>:<password>@updates.dnsomatic.com/nic/update?hostname=However, it seems that now they have done some changes because all is working fine
hope this helps
Please sign in to leave a comment.
Comments
30 comments