[Test] Asuswrt-Merlin with HTTPS support for DDNS

[RMerlin]

Hi everyone,

I need people to test a new version of ez-ipupdate that now supports HTTPS for updating your DDNS service (previously ez-ipupdate only supported HTTP - that's right, zero encryption...)

https://asuswrt.lostrealm.ca/test-builds

The builds are in the DDNS Test folder:

Please report which DDNS provider you are using, and your results (good or bad).

These builds are ONLY intended for testing DDNS services.

Tested OK:
DNS-o-Matic
No-IP
Namecheap
Asus
DynDNS

 

[Gingernut]

Using DNSomatic to update my DuckDNS DNS service.

 start_ddns: update WWW.DNSOMATIC.COM dnsomatic, wan_unit 0
Sep  1 09:52:52 ddns_update: ez-ipupdate: starting...
Sep  1 09:52:52 ddns_update: connected to updates.dnsomatic.com (**.215.92.***) on port 443.
Sep  1 09:52:53 ddns_update: request successful
Sep  1 09:52:53 ddns_update: asusddns_update: 0
Sep  1 09:52:53 ddns: ddns update ok

Test build seems to work fine.

 

[Zastoff]

Sep  1 10:14:33 start_ddns: update WWW.ASUS.COM dyndns, wan_unit 0
Sep  1 10:14:33 ddns_update: ez-ipupdate: starting...
Sep  1 10:14:33 ddns_update: asus_private() interface =eth0
Sep  1 10:14:33 ddns_update: g_asus_ddns_mode == 2
Sep  1 10:14:34 ddns_update: connected to nwsrv-ns1.asus.com (103.10.4.108) on port 443.
Sep  1 10:14:34 ddns_update: Asus update entry:: return: HTTP/1.1 200 OK^M Date: Sat, 01 Sep 2018 08:14:33 GMT^M Server: Apache^M X-Powered-By: PHP/5.6.30^M Content-Length: 0^M Connection: close^M Content-Type: text/html; charset=UTF-8^M ^M
Sep  1 10:14:34 ddns_update: retval= 0, ddns_return_code (,200)
Sep  1 10:14:34 ddns_update: asusddns_update: 0
Sep  1 10:14:34 ddns: ddns update ok

Test build seems to work, Not sure about the return entry. But this is what i get.

edit: Guess the ddns_return_code (,200) is : This class of status code indicates that the client's request was successfully received, understood, and accepted

 

[Xentrk]

I tested with DNS-O-Matic paired with ydns.io

Sep  1 16:59:59 watchdog: start ddns.
Sep  1 16:59:59 rc_service: watchdog 363:notify_rc restart_ddns
Sep  1 16:59:59 start_ddns: update WWW.DNSOMATIC.COM dnsomatic, wan_unit 0
Sep  1 17:00:00 ddns_update: ez-ipupdate: starting...
Sep  1 17:00:04 ddns_update: connected to updates.dnsomatic.com (67.215.92.215) on port 443.
Sep  1 17:00:06 ddns_update: request successful
Sep  1 17:00:06 ddns_update: asusddns_update: 0
Sep  1 17:00:09 ddns: ddns update ok
Sep  1 17:00:09 ddns_update: exit_main

 

[thelonelycoder]

Using asus.com on the RT-AC86U. Success.

Sep  1 16:29:02 rc_service: watchdog 783:notify_rc restart_ddns
Sep  1 16:29:02 start_ddns: update WWW.ASUS.COM dyndns, wan_unit 0
Sep  1 16:29:02 ddns_update: ez-ipupdate: starting...
Sep  1 16:29:02 ddns_update: asus_private() interface =eth0
Sep  1 16:29:02 ddns_update: g_asus_ddns_mode == 2
Sep  1 16:29:03 ddns_update: connected to nwsrv-ns1.asus.com (103.10.4.108) on port 443.
Sep  1 16:29:04 ddns_update: Asus update entry:: return: HTTP/1.1 200 OK^M Date: Sat, 01 Sep 2018 14:29:03 GMT^M Server: Apache^M X-Powered-By: PHP/5.6.30^M Content-Length: 0^M Connection: close^M Content-Type: text/html; charset=UTF-8^M ^M
Sep  1 16:29:04 ddns_update: retval= 0, ddns_return_code (,200)
Sep  1 16:29:04 ddns_update: asusddns_update: 0
Sep  1 16:29:04 ddns: ddns update ok
Sep  1 16:29:04 ddns_update: exit_main

 

[Striker317]

Namecheap works....
Sep 1 11:15:40 start_ddns: update WWW.NAMECHEAP.COM namecheap, wan_unit 0
Sep 1 11:15:40 ddns_update: ez-ipupdate: starting...
Sep 1 11:15:41 ddns_update: connected to dynamicdns.park-your-domain.com (104.219.249.157) on port 443.
Sep 1 11:15:41 ddns_update: request successful
Sep 1 11:15:41 ddns_update: asusddns_update: 0
Sep 1 11:15:41 ddns: ddns update ok
Sep 1 11:15:41 ddns_update: exit_main

but
it breaks with let's encrypt

i have put
hostname: home
domain name: customname.com

won't generate a certificate.

previously, I'd put hostname: home.customname.com when using custom ddns-script file and then it works.

unfortunately, putting home.customname.com for my hostname generates an error.

 

[Striker317]

dnsomatic works

Sep 1 11:24:58 start_ddns: update WWW.DNSOMATIC.COM dnsomatic, wan_unit 0
Sep 1 11:24:58 ddns_update: ez-ipupdate: starting...
Sep 1 11:24:58 ddns_update: connected to updates.dnsomatic.com (67.215.92.215) on port 443.
Sep 1 11:24:59 ddns_update: request successful
Sep 1 11:24:59 ddns_update: asusddns_update: 0
Sep 1 11:24:59 ddns: ddns update ok
Sep 1 11:24:59 ddns_update: exit_main

however, won't generate a certificate similar to above.

 

[RMerlin]

Doesn't Let's Encrypt require the use of Asus's own DDNS, to achieve DNS-based validation?

 

[Striker317]

Doesn't Let's Encrypt require the use of Asus's own DDNS, to achieve DNS-based validation?

I got a let’s encrypt certificate working with my home.customname.com hostname through Namecheap via a custom ddns-start script

 

[RMerlin]

edit: Guess the ddns_return_code (,200) is : This class of status code indicates that the client's request was successfully received, understood, and accepted

Correct. Asus uses many standard HTTP response code to provide results. 401 would be an authentication failure for example. 200 indicates the update was successful.

 

[RMerlin]

I got a let’s encrypt certificate working with my home.customname.com hostname through Namecheap via a custom ddns-start script

Then this has nothing to do with ez-ipupdate. The test is simply to determine if HTTPS-based update work, it won't add LE support to services that didn't previously have it.

 

[nash16]

It is working with free-dns and 86U, thx Eric!

 

[Striker317]

Then this has nothing to do with ez-ipupdate. The test is simply to determine if HTTPS-based update work, it won't add LE support to services that didn't previously have it.

Understood.

Not sure if it worth adding a note that let’s encrypt isn’t supported for anything other than Asus’s DDNS?

 

[Zastoff]

https://github.com/kvic-z/pixelserv...ixelserv-CA-to-issue-a-certificate-for-WebGUI

 

[RMerlin]

Understood.

Not sure if it worth adding a note that let’s encrypt isn’t supported for anything other than Asus’s DDNS?

Asus never made it clear what was actually required. During development, they even added a second lighttpd instance to the firmware, probably so it could handle LE validation even with third party DDNS services. Since I couldn't keep track of their work, I never knew for sure if that particular feature was ever finalized or not.

 

[RMerlin]

It is working with free-dns and 86U, thx Eric!

There are no "free-dns" service in Asuswrt. Which actual provider were you using?

 

[SMS786]

About to give the test run a spin on my 68U. Can anyone confirm whether these are built upon the 384.6 codebase?

 

[thelonelycoder]

About to give the test run a spin on my 68U. Can anyone confirm whether these are built upon the 384.6 codebase?

384.7_alpha2

 

[bubobih]

work ok on 86u (asus dns + le dont work)

 

[nash16]

There are no "free-dns" service in Asuswrt. Which actual provider were you using?

I'm using: https://freedns.afraid.org/