Tailscale adds a new IP to the system, which is by default however only used when you access other IPs from the same subnet. So it does not affect any other network connections, and it does not affect dietpi-ddns updates.
Honestly can you describe your use case more in detail. For what reason you use Tailscale and what do you plan to do with the DDNS? You don’t need to have a DDNS while using Tailscale.
It might be I need to learn more
Thank you for your patience.
I’m using tailscale because CGNAT doesn’t allow me to port forward.
I’m the using the tailscale IP via Duck DNS to assign a name to the nextcloud NAS server.
If my girlfriend uninstalls or resets tailscale, she’ll get a new IP. I want her to be able to reconnect to her photos without me getting involved to set things straight.
I’m not sure if the written IPs works (magic DNS? ), at least for now, picking up the installation tomorrow as I’m on holidays.
Indeed. If your Nextcloud instance can/shall be available through Tailscale only, you can just choose an appropriate hostname within your Tailscale network and use it for DNS at the clients. DDNS is not required at all in that case, as Tailscale manages everything.
It would be an honor, making no promises.
I have managed to set it up for multiplatform, Linux, Android, Windows 11
I cannot promise on the coding either, because I use “the unspoken” for everything
PS: I would like first to finish the Cloud-NAS setup with automated reduncy backups.
Depends if you enable automatically redirect from http to https. And some more information would be needed what address you are using at home. Is it that the same you use while outside your home?
PS: On my Androids I could go through some warnings whether i trust the page, dietpidevice.name-name.ts.net or not, and it did work.
However, on my Window 11 this is still like above.
Gave me an idea, I tried https://192.168.111.99/nextcloud/, thus specifying with https://, and also on Windows i received the unsafe warning, but I got through and it works