bad auth
Suddenly from yesterday morning I'm getting 'bad auth' responses from a tried-and-true inadyn configuration that's been working for almost a year... is anyone else running into problems? I'm scratching my head... tried changing passwords, tried non-ssl updates, can't get anywhere. I have a ticket open as well, but just wondering if maybe it's a broader service issue or some change that I need to implement...
-
I've been pulling my hair out since yesterday. Seems I'm not the only one. Any update yet?
Been working reliably for years on my trusty FRITZ!Box, but now failing with BADAUTH. I can confirm this is an account issue as I tried working around this by using a Windows updater, but got the same issue with credentials.
-
I am having the same issue since yesterday as well. It is a DNS-O-Matic issue somewhere on their side. This is the result from a command line curl to their API:
< HTTP/2 401
< date: Wed, 08 Dec 2021 03:13:47 GMT
< server: opendns
* Authentication problem. Ignoring this.
< www-authenticate: Basic realm="DNSOMATIC"
< content-type: text/html; charset=UTF-8
< x-envoy-upstream-service-time: 42
< x-xss-protection: 1; mode=block
< x-ingress-point: dfw
< strict-transport-security: max-age=31536000; includeSubDomainsIt is not an "unauthorized" error which implies wrong user/password, but some other authorization issue they are having. My config has not changed in months and stopped working yesterday on its own.
-
DNS-O-Matic is a free service. When it works, it works brilliantly. However, when there's a problem, being free, there's no well defined SLA. This is day 3 of the issue. If you're doing anything serious, like serving customer websites, DNS-O-Matic represents a weak link in the chain.
This incident has made me realise that I need to switch to a static IP, and I have. I've moved from a very stressful situation not knowing when the broken DNS-O-Matic service would be restored, with no ongoing updates from OpenDNS support or Cisco, the parent company, to great relief for myself several small business customers I service. It's a hard lesson to learn.
Once DNS-O-Matic services are restored, I'll still use it in non-critical situations e.g. access to an offsite backup site, but I will definitely avoid it where I have SLAs with my own customers. The AUD$10 per month for a static IP is well worth the investment compared to the stress and worry of being dependent on a third party providing a free service.
-
Slightly annoying as thought it was Merlin's new firmware in testing that was the cause as a previous version had to content with dnsomatic API/Parameter changes.
Let's hope dnsomatic/opendns fix this as many routers that update DDNS are likely to be failing right now.
Static IP not an option for home users in many cases from various ISP's, especially if you have a choice of just ONE gigabit provider because the rest are on slower ancient copper.
-
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: -
+1 here - other thread here on the same issue https://support.opendns.com/hc/en-us/community/posts/4412375273492-DNSOMATIC-401-Unauthorized-badauth
Please sign in to leave a comment.
Comments
20 comments