Just to give my piece of information on the topic.
I had for quite a long time the same problem, and could not determine which was the root of the problem.
Finally i choose to remove any special characters in the password (that worked for many years) and suddenly everything started working again.
Only used number, lower-case and upper-case.
Could not determine if the problem is caused in ddwrt or in dnsomatic, but it anyway removing the special character made it work.
Excuse a noob here, but what exactly is the difference between having a DDNS service like no-ip for example and DNS-o-Matic?
DDNS services update your dynamic IP by themselves don't they? what need is there for DNS-o-Matic then?
DSN-O-Matic simply forwards your IP to different DDNS services, it's a convenient solution when other solutions fail. So you only need to use it if you have no alternative or if you use multiple services, like OpenDNS and NO-IP at the same time. _________________ 2 times RT-AC56U running 33772 with entware-ng, Yamon 3 (SFE disabled).
Asus RT-N16 running Merlin LTS fork RT-N16_3.0.0.4_374.43_2-25E8j9527.trx with entware-ng.
2 times Asus RT-N16 running dd-wrt.v24-33772_NEWD-2_K3.x_big.bin with entware-ng
Just to give my piece of information on the topic.
I had for quite a long time the same problem, and could not determine which was the root of the problem.
Finally i choose to remove any special characters in the password (that worked for many years) and suddenly everything started working again.
Only used number, lower-case and upper-case.
Could not determine if the problem is caused in ddwrt or in dnsomatic, but it anyway removing the special character made it work.
This was the exact problem I was having. I had an "&" in my password and it was causing the update to fail. I would imagine this is because the password does not get URL encoded before being sent, and so any characters that are significant in a URL (like '?', '=', and '&') will likely cause the same issue.
Since OpenDNS has changed their password requirements so that passwords now MUST have at least one special character, make sure you avoid those 3 at least.
on left side is my dnsomatic user/password, and the only special char in password is a "dot" (.)
on the right side is my user/pass for google domains, which i had working previously with ddns under openwrt.
I'm willing to bet the dot in your password is the issue. Try changing it to letters/numbers only and see if it works, then change the password to include more complexity once you've validated the configuration is correct and working. _________________ R7000 Nighthawk - DD-WRT v3.0-r40270M kongac (07/11/19)
~~~~~~~~~~~~~~Currently Unused~~~~~~~~~~~~~~
WRT54Gv2 - V24 STD Build 22118 configured as AP
WRT54Gv8.2 - V24 Micro Build 22118 configured as AP
dnsomatic requires the password to have a special character. I've tried @ $ . none of them work, I'm thinking it might be someother problem? Do you have a recommendation of which special character to use?
HalfBit wrote:
tapr00t wrote:
Anyone know what I'm doing wrong?
on left side is my dnsomatic user/password, and the only special char in password is a "dot" (.)
on the right side is my user/pass for google domains, which i had working previously with ddns under openwrt.
I'm willing to bet the dot in your password is the issue. Try changing it to letters/numbers only and see if it works, then change the password to include more complexity once you've validated the configuration is correct and working.
dnsomatic requires the password to have a special character. I've tried @ $ . none of them work, I'm thinking it might be someother problem? Do you have a recommendation of which special character to use?
HalfBit wrote:
tapr00t wrote:
Anyone know what I'm doing wrong?
on left side is my dnsomatic user/password, and the only special char in password is a "dot" (.)
on the right side is my user/pass for google domains, which i had working previously with ddns under openwrt.
I'm willing to bet the dot in your password is the issue. Try changing it to letters/numbers only and see if it works, then change the password to include more complexity once you've validated the configuration is correct and working.
I think I have a + in mine. You could try that. _________________ R7000 Nighthawk - DD-WRT v3.0-r40270M kongac (07/11/19)
~~~~~~~~~~~~~~Currently Unused~~~~~~~~~~~~~~
WRT54Gv2 - V24 STD Build 22118 configured as AP
WRT54Gv8.2 - V24 Micro Build 22118 configured as AP
Joined: 05 Feb 2017 Posts: 7 Location: Buenos Aires, Argentina
Posted: Tue Jul 09, 2019 2:42 Post subject:
tapr00t wrote:
Yeah, still doesn't work, same error, I'm stumped.
I think I have a + in mine. You could try that.[/quote][/quote]
Hi,
Did you try with " /nic/update?hostname= " ?.
That is the way that works for me.
The first slash (/) looks like be important. Try it and tell us if works for you.
Regards!.
Yeah, still doesn't work, same error, I'm stumped.
I think I have a + in mine. You could try that.
[/quote]
Hi,
Did you try with " /nic/update?hostname= " ?.
That is the way that works for me.
The first slash (/) looks like be important. Try it and tell us if works for you.
Regards!.[/quote]
with that change I'm getting a "401 unauthorized" error, before I was getting a "400 bad request" error
