#19 DNS-O-Matic update fails following redirect (301)

[ehf7bkng]

Hi. Wasn't sure where to raise this so apologies if it's the wrong place.

Not sure if this has only just started happening but, I've just noticed that my updates to DNS-O-Matic are failing.

It looks to me like the original request is sent via HTTP, and DNS-O-Matic are redirecting this (via a 301) to HTTPS, which then fails because the credentials are not being passed. I tested this with curl with and without using the "--location" option and the results are the same.

Jul 22 15:10:51 server inadyn[116249]: Wed Jul 22 15:10:51 2020: N:INADYN: DYNDNS my Request:
Jul 22 15:10:51 server inadyn[116249]: GET /nic/update?system=dyndns&hostname=all.dnsomatic.com&myip={My IP}&wildcard=OFF&mx=all.dnsomatic.com&backmx=NO&offline=NO HTTP/1.0
Jul 22 15:10:51 server inadyn[116249]: Host: updates.dnsomatic.com
Jul 22 15:10:51 server inadyn[116249]: Authorization: Basic xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Jul 22 15:10:51 server inadyn[116249]: User-Agent: inadyn-mt/02.28.10_audible bhoover@wecs.com 
Jul 22 15:10:51 server inadyn[116249]:  
Jul 22 15:10:51 server inadyn[116249]: Wed Jul 22 15:10:51 2020: W:INADYN: Error validating DYNDNS svr answer. Check usr,pass,hostname!
Jul 22 15:10:51 server inadyn[116249]: Wed Jul 22 15:10:51 2020: C:INADYN:
Jul 22 15:10:51 server inadyn[116249]: **********************************************************************
Jul 22 15:10:51 server inadyn[116249]: Fatal dyndns server update error for alias, all.dnsomatic.com.
Jul 22 15:10:51 server inadyn[116249]: This client should be stopped and corrected for configuration errors, and restarted... 
Jul 22 15:10:51 server inadyn[116249]: **********************************************************************
Jul 22 15:10:51 server inadyn[116249]: Wed Jul 22 15:10:51 2020: W:INADYN: DYNDNS Server response: 
Jul 22 15:10:51 server inadyn[116249]: HTTP/1.0 301 Moved Permanently
Jul 22 15:10:51 server inadyn[116249]: location: https://updates.dnsomatic.com/nic/update?system=dyndns&hostname=all.dnsomatic.com&myip={My IP}&wildcard=OFF&mx=all.dnsomatic.com&backmx=NO&offline=NO
Jul 22 15:10:51 server inadyn[116249]: date: Wed, 22 Jul 2020 14:10:50 GMT
Jul 22 15:10:51 server inadyn[116249]: server: opendns
Jul 22 15:10:51 server inadyn[116249]: connection: close
Jul 22 15:10:51 server inadyn[116249]: content-length: 0
Jul 22 15:10:51 server inadyn[116249]:  
Jul 22 15:10:51 server inadyn[116249]: Wed Jul 22 15:10:51 2020: W:DYNDNS: Failed updating alias table...
Jul 22 15:10:51 server inadyn[116249]: Wed Jul 22 15:10:51 2020: W:'RC_DYNDNS_RSP_CONFIG' (0x49) updating the IPs. (it 0)

Is there a way to use HTTPS by default, or pass the credentials following the redirect?

If you need any more information, let me know.

Thanks.

[Bryan Hoover]

Right, seems to be https related. Take a look at:

https://sourceforge.net/p/inadyn-mt/discussion/751470/thread/3f7c4a6c00/

[ehf7bkng]

Thanks for the quick response. Are there any plans to add native support for HTTPS, or will stunnel be the only option?

[Bryan Hoover]

Thanks for your questions!  I think the modularity of an ssl adaptor is a more robust solution.