What's new

DDNS with DNSOMATIC ???

WindyT

New Around Here
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

Part of the Furniture
I use dns-o-matic on Asuswrt-Merlin:

1600137146523.png
 

WindyT

New Around Here

retuor

Occasional Visitor
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:

Code:
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

New Around Here
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:

Code:
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

Occasional Visitor
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

New Around Here
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.
 

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top