DDNS with DNSOMATIC ???

[WindyT]

Hi, I am trying to setup my DDNS but it keeps failing. Reading the past posts there was a suggestion to use: "all.dnsomatic.com" for the host value but it still does not work. Anybody got this working please?

Server: www.dnsomatic.com (selected from dropdown)
Host: all.dnsomatic.com (also tried my specific subdomain i.e. asus.domain.com and other value)
Username or email: username (was told email does not work)
Password: Mypassw0rd
Wildcard: NO
Verification: No (tried YES as well)
SSL Cert: NO

System log:
Sep 14 17:19:19 watchdog: start ddns.
Sep 14 17:19:19 rc_service: watchdog 1095:notify_rc start_ddns
Sep 14 17:19:19 start_ddns: update WWW.DNSOMATIC.COM dnsomatic, wan_unit 0
Sep 14 17:19:19 ddns update: ez-ipupdate: starting...
Sep 14 17:19:19 ddns update: connected to updates.dnsomatic.com (146.112.255.155) on port 80.
Sep 14 17:19:20 ddns update: unknown return code: 301
Sep 14 17:19:20 ddns update: server response: Moved Permanently
Sep 14 17:19:20 ddns update: asusddns_update: 1
Sep 14 17:19:20 ddns update: exit_main

 

[Xentrk]

I use dns-o-matic on Asuswrt-Merlin:

 

[dave14305]

It wants to redirect http://updates.dnsomatic.com/nic/update to https://updates.dnsomatic.com/nic/update but I'm speculating that ASUS stock firmware doesn't have HTTPS support built into ez-ipupdate.

 

[WindyT]

It wants to redirect http://updates.dnsomatic.com/nic/update to https://updates.dnsomatic.com/nic/update but I'm speculating that ASUS stock firmware doesn't have HTTPS support built into ez-ipupdate.

So I am fracked, unless I flash the Merlin...

Thanks.

Do you guys know if Merlin allows to set a specific LAN port on it's own VLAN? That would make me to start flashing (4 routers, 4 locations 500 miles from each other...)

 

[retuor]

DNSOMATIC works for me on ASUSWRT. Never had an issue with past up to current firmware versions.

I use same settings except for username I use email.

Maybe it's a setting on DNSOMATIC side? How about create a new account and test?

My system log:

Sep 12 18:57:28 start_ddns: update WWW.DNSOMATIC.COM dnsomatic, wan_unit 0
Sep 12 18:57:28 ddns update: ez-ipupdate: starting...
Sep 12 18:57:28 dhcp client: bound XXX.XXX.XXX.XXX/255.255.252.0 via XXX.XXX.XXX.XXX for 600 seconds.
Sep 12 18:57:28 ddns update: connected to updates.dnsomatic.com (146.112.255.155) on port 443.
...
Sep 12 18:57:29 ddns update: request successful
Sep 12 18:57:29 ddns update: asusddns_update: 0
Sep 12 18:57:29 ddns: ddns update ok
Sep 12 18:57:29 ddns update: exit_main

 

[WindyT]

DNSOMATIC works for me on ASUSWRT. Never had an issue with past up to current firmware versions.

I use same settings except for username I use email.

Maybe it's a setting on DNSOMATIC side? How about create a new account and test?

My system log:

Sep 12 18:57:28 start_ddns: update WWW.DNSOMATIC.COM dnsomatic, wan_unit 0
Sep 12 18:57:28 ddns update: ez-ipupdate: starting...
Sep 12 18:57:28 dhcp client: bound XXX.XXX.XXX.XXX/255.255.252.0 via XXX.XXX.XXX.XXX for 600 seconds.
Sep 12 18:57:28 ddns update: connected to updates.dnsomatic.com (146.112.255.155) on port 443.
...
Sep 12 18:57:29 ddns update: request successful
Sep 12 18:57:29 ddns update: asusddns_update: 0
Sep 12 18:57:29 ddns: ddns update ok
Sep 12 18:57:29 ddns update: exit_main

What version of the FMW are you using? This is the difference:

yours:
connected to updates.dnsomatic.com (146.112.255.155) on port 443

Mine:
connected to updates.dnsomatic.com (146.112.255.155) on port 80.

As stated above DNSOMATIC requires SSL, if I can force my router to use HTTPS instead it would be great!

 

[retuor]

Yeah, I noticed that when I first posted.

I didn't notice anything special in my DDNS config page. It has the same options that you listed.
And by special I mean use port 443 instead of port 80.

I'm using RT-AC86U's latest firmware. It's not by choice. It's because of the recent auto-update.

Also I've never had issues with DDNS, specifically configured to DNSOMATIC, with past firmwares. And of course I don't have the system log entries saved to see if it connected with 443 or 80 or whatever port.

Would a reboot or more drastically a reset and re-configure help? If you do reset, make sure to save the settings first.

What version of the FMW are you using? This is the difference:

yours:
connected to updates.dnsomatic.com (146.112.255.155) on port 443

Mine:
connected to updates.dnsomatic.com (146.112.255.155) on port 80.

As stated above DNSOMATIC requires SSL, if I can force my router to use HTTPS instead it would be great!

 

[WindyT]

OK, so I tried on my brother's RT-AC68U and it works - annoying Asus bug :-(

I have a case open but my hopes are very, very low...

T.

 

[WindyT]

OK, I updated the firmware manually to 3.0.0.4.384_9566 and the SSL issue is fixed, the firmware seems less stable so proceed with caution....

 

[Christian_Haitian]

Greetings,

Just reporting that as of October 27, 2020, dnsomatic made a system change that seems to have broken the update method used in Merlin's AsusWrt 384.19 firmware for dnsomatic.com. See here for more info of what I think has caused the issue as it worked fine for until around that day when my router attempted to force an update and failed. To workaround the issue, I had to setup a custom update as outlined here. It was easy enough to do since there was a good dnsomatic custom script here that made it mostly cut and paste via a ssh session.

 

[duzuhaha]

Greetings,

Just reporting that as of October 27, 2020, dnsomatic made a system change that seems to have broken the update method used in Merlin's AsusWrt 384.19 firmware for dnsomatic.com. See here for more info of what I think has caused the issue as it worked fine for until around that day when my router attempted to force an update and failed. To workaround the issue, I had to setup a custom update as outlined here. It was easy enough to do since there was a good dnsomatic custom script here that made it mostly cut and paste via a ssh session.

thank you, you save my life.

endup not using ddns feature from router, but running a .sh script from your link https://github.com/RMerl/asuswrt-merlin.ng/wiki/DDNS-Sample-Scripts#dns-o-matic by a crontab job to solve the problem