learning_curve
Senior Member
The final re-edited / updated / posted errors removed, version of all of this now:
The setup that I was using was as follows: Asus DDNS **.asuscomm.com is configured via the GUI page: **/Advanced_ASUSDDNS_Content.asp & No-IP DDNS **.ddns.net was configured via CLI in a new file here: /jffs/configs/inadyn.conf.add When the DDNS client / service was restarted, the two were correctly combined within this file: /etc/inadyn.conf and the dual source DDNS was fully operational. The Let's Encrypt SSL Certificate was easily issued / re-issued etc and things were looking good at that point. However... an IPv6 DDNS service can only be provided by the No-IP DDNS service as the ASUS DDNS service is still apparently IPv4 only at present (although the coding is in place it seems...) So... I went back to reading all of this again: https://github.com/RMerl/asuswrt-merlin.ng/wiki/DDNS-services plus this: http://www.snbforums.com/threads/inadyn-configuration-files.72130/post-684701 plus this inadyn data https://github.com/troglobit/inadyn#configuration and even this broad overview / simplified version: https://fossies.org/linux/inadyn/man/inadyn.conf.5 just for good measure. All make perfect sense.
Although there's three different options available, I chose to create an original inadyn.conf file, store it in /jffs/configs/ which then, as all of the relative guidance above clearly says, completely replaces the config file generated by the firmware, which indeed it does and so it all works perfectly (including IPv6 DDNS).
It seems that the ONLY remaining issue (not one that causes any actual problems other than far too much logging, but it is still an unnecessary issue) is one that's been here for a while now, which is; the regular re-start of the DDNS service, because of the involvement with IPv6. This aspect is NOT covered in ANY of the above because the notify_rc("restart_ddns"); command ONLY takes place IF your router uses IPv6 & DDNS.
See the following posts (my errors removed / corrected) in this thread, for more relevant after-thoughts to this issue too.
The setup that I was using was as follows: Asus DDNS **.asuscomm.com is configured via the GUI page: **/Advanced_ASUSDDNS_Content.asp & No-IP DDNS **.ddns.net was configured via CLI in a new file here: /jffs/configs/inadyn.conf.add When the DDNS client / service was restarted, the two were correctly combined within this file: /etc/inadyn.conf and the dual source DDNS was fully operational. The Let's Encrypt SSL Certificate was easily issued / re-issued etc and things were looking good at that point. However... an IPv6 DDNS service can only be provided by the No-IP DDNS service as the ASUS DDNS service is still apparently IPv4 only at present (although the coding is in place it seems...) So... I went back to reading all of this again: https://github.com/RMerl/asuswrt-merlin.ng/wiki/DDNS-services plus this: http://www.snbforums.com/threads/inadyn-configuration-files.72130/post-684701 plus this inadyn data https://github.com/troglobit/inadyn#configuration and even this broad overview / simplified version: https://fossies.org/linux/inadyn/man/inadyn.conf.5 just for good measure. All make perfect sense.
Although there's three different options available, I chose to create an original inadyn.conf file, store it in /jffs/configs/ which then, as all of the relative guidance above clearly says, completely replaces the config file generated by the firmware, which indeed it does and so it all works perfectly (including IPv6 DDNS).
It seems that the ONLY remaining issue (not one that causes any actual problems other than far too much logging, but it is still an unnecessary issue) is one that's been here for a while now, which is; the regular re-start of the DDNS service, because of the involvement with IPv6. This aspect is NOT covered in ANY of the above because the notify_rc("restart_ddns"); command ONLY takes place IF your router uses IPv6 & DDNS.
See the following posts (my errors removed / corrected) in this thread, for more relevant after-thoughts to this issue too.
Last edited: