As of October 2025, Inadyn is no longer maintained

[XIII]

As of October 2025, this project has been archived and is no longer maintained.

After many years of development and community contributions, maintenance on this repository has ended. The source code remains available for reference and for anyone who wishes to continue development in their own fork.

— Joachim Wiberg (troglobit)

GitHub - troglobit/inadyn: In-a-Dyn is a dynamic DNS client with multiple SSL/TLS library support

In-a-Dyn is a dynamic DNS client with multiple SSL/TLS library support - troglobit/inadyn

github.com

 

[XIII]

@RMerlin Any chance of including the final release in the next beta?

(I’d like to use the Porkbun DDNS without my custom script)

https://github.com/troglobit/inadyn/releases/tag/v2.13.0

 

[RMerlin]

Not really surprised, based on some of the more recent posts on social medias by its developer.

@RMerlin Any chance of including the final release in the next beta?

No. I have been unable to keep up-to-date with it for a few years already because since Asus integrated my work into the stock firmware, they've made extensive changes to its code, making it difficult to keep their modified code in sync with upstream. The only way that would be possible to update would be to ditch all their changes that they made for IPv6 support. And I'm not sure if they did the same level of extensive changes for Asus DDNS. I had initially implemented it as a plugin with almost no changes to the core code itself, like any other DDNS provider. That has changed afterward as they modified the authentication method used by Asus DDNS, and I believe that code has spread outside of the plugin code itself.

So, updating inadyn, if it ever happen, would be a major project of its own, definitely not something that would fit within the current 102.6 development cycle.

I hate it when they do that (changing open source project codes) because of that. It makes it nearly impossible to keep up-to-date with the upstream changes. One of the reasons why I never kept in sync with their own OpenVPN implementation and went my own way, limiting the amount of changes applied to the OpenVPN code itself. Same with busybox - they (and Broadcom) have made changes all over the place. Back in the day, just upgrading to 1.25 was a significant undertaking by themiron.