Looking at the client request to the update.opendns.com server, it seems that it the Authorization: Basic **** header wasn't being honered. After looking through a number of discussions, this thread mentioned that a client (I assumed the OpenDNS updater cannot handle special character, but they require your password to have them :shrug:). I went and updated my password and removed all special characters except for one, and it seemed to work. I am not sure if this is due to the updater web server /nic/update?system=dyndns&hostname=&myip= HTTP/1.0 or the ddclient itself.
This is just a reaching out to give some context on something I found out today, and just wanted to make your team aware.
Thanks for the client and best of luck.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
(by the way, I see that you have a myip= in your URI - from my discussions with opendns support a couple months, they broke that feature 6 months ago or so. The requests have to come from the IP, and can no longer use the myip= parameter)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Actually, I see that opendns is deprecating their API, and switching to dnsomatic.com. I just switched my client to use updates.dnsomatic.com instead of updates.opendns.com, maybe that will fix your problem.
Though it turns out that though they say they accept the myip= parameter, and return a 200 HTTP status code, after I login to opendns.com, they say, "The IP Address you have supplied to DNS-O-Matic
differs from the IP Address that you are coming from. OpenDNS does not allow you to update to an IP Address that you don't actually own."
Too bad.
Last edit: Jonathan Daley 2017-10-18
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Do you have an URL where you found the info about deprecation an dswitch to dnsomatic? I think we should change the default on ddclient if that's the case.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
updates.opendns.com works, so I don't know why someone said to change it to updates.dnsomatic.com.
In any event, be careful when changing your OpenDNS email account e-mail if you use it in the ddclient.conf configuration. I got the error message the OP describes when I had login= set to the wrong e-mail address. The username is impervious to e-mail changes, so it might be better to use it there.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I spent some time today trying to resolve the following issue
Looking at the client request to the update.opendns.com server, it seems that it the
Authorization: Basic ****header wasn't being honered. After looking through a number of discussions, this thread mentioned that a client (I assumed the OpenDNS updater cannot handle special character, but they require your password to have them :shrug:). I went and updated my password and removed all special characters except for one, and it seemed to work. I am not sure if this is due to the updater web server /nic/update?system=dyndns&hostname=&myip= HTTP/1.0 or the ddclient itself.This is just a reaching out to give some context on something I found out today, and just wanted to make your team aware.
Thanks for the client and best of luck.
Hi,
Thanks for letting us know. Does your password work on http://dashboard.opendns.com/ as mentioned in
https://support.opendns.com/hc/en-us/community/posts/220039927/comments/224649867?
If it works on the dashboard we should escape the password when using it to login. I'll try to find out what extra we can do.
See the Note 3 where it talks about escaping characters.
https://support.opendns.com/hc/en-us/articles/227987727
(by the way, I see that you have a myip= in your URI - from my discussions with opendns support a couple months, they broke that feature 6 months ago or so. The requests have to come from the IP, and can no longer use the myip= parameter)
Actually, I see that opendns is deprecating their API, and switching to dnsomatic.com. I just switched my client to use updates.dnsomatic.com instead of updates.opendns.com, maybe that will fix your problem.
Though it turns out that though they say they accept the myip= parameter, and return a 200 HTTP status code, after I login to opendns.com, they say, "The IP Address you have supplied to DNS-O-Matic
differs from the IP Address that you are coming from. OpenDNS does not allow you to update to an IP Address that you don't actually own."
Too bad.
Last edit: Jonathan Daley 2017-10-18
Do you have an URL where you found the info about deprecation an dswitch to dnsomatic? I think we should change the default on ddclient if that's the case.
updates.opendns.com works, so I don't know why someone said to change it to updates.dnsomatic.com.
In any event, be careful when changing your OpenDNS email account e-mail if you use it in the ddclient.conf configuration. I got the error message the OP describes when I had login= set to the wrong e-mail address. The username is impervious to e-mail changes, so it might be better to use it there.