4 ms·
> I think a DDNS client per device is the simplest solution. With https://dns.he.net https://dns.he.net, this can be an hourly cron job that fetches a URL, so n
by TheHappyOddish 3y ago
> I think a DDNS client per device is the simplest solution. With https://dns.he.net https://dns.he.net, this can be an hourly cron job that fetches a URL, so no additional software is needed.
Sure, but depending on what you have set up a lot of maintenance and complexity compared to NAT.
> Alternatively, if your devices have a stable suffix, https://dynv6.com/ https://dynv6.com/ supports prefix updates across multiple records.
That is cool and interesting, thanks! Like a lot of people self hosting, the hosted nature of it is unappealing to be, but the concept is workable with a self-hosted solution for sure.