cup VS caddy-dynamicdns

You should be able to grab the latest linux executable here: https://github.com/viertaxa/cup/releases, unzip it, and run the application that way.

This plugin for dynamic DNS: https://github.com/mholt/caddy-dynamicdns, supports any of these DNS providers you find on this page https://github.com/orgs/caddy-dns/repositories?type=source. You can use DuckDNS for example which is also a free domain.

Sure, you can do this with nginx and dynamic DNS if you really want to, but Caddy does it all for you, with automatic HTTPS, and runs natively on Android (or in Termux): https://caddy.community/t/running-caddy-2-on-android/13993?u...

Here's the dynamic DNS plugin: https://github.com/mholt/caddy-dynamicdns -- it will just update the A records for your domain directly with your DNS provider, no need for a third-party service.

Re 3: What you really need is Caddy [0] with this dynamic DNS module: https://github.com/mholt/caddy-dynamicdns

Caddy has state-of-the-art certificate automation and TLS support, and with that module, it automatically updates DNS records if users have non-static IPs. It'll also serve certs for localhost domains (use *.localhost IMO).

[0]: https://caddyserver.com (I'm the author, for disclosure)

Caddy has a (WIP) dynamic DNS module that will keep your records updated for you: https://github.com/mholt/caddy-dynamicdns

Neat. I had a similar frustration so I wrote a dynamic DNS module for Caddy; https://github.com/mholt/caddy-dynamicdns - it can be extended to work with any dns provider that has an api. (It's what I currently use with Cloudflare)