You can run dyndns yourself if your dns provider has an API (e.g. cloudflare). Mine is a ~10 line bash script. Basic idea is `curr_ip=$(curl ifconfig.me | grep

You can run dyndns yourself if your dns provider has an API (e.g. cloudflare). Mine is a ~10 line bash script. Basic idea is `curr_ip=$(curl ifconfig.me | grep smth)`, then `curl -X POST https://your_dns_provider?dn=vpn.jtode.com&new_ip=$curr_ip https://your_dns_provider?dn=vpn.jtode.com&new_ip=$curr_ip`. Run it as a cron, on a schedule that's kind to your IP identification service and kind to your personal SLAs around uptime (mine's set to every 5 minutes). Verizon changes my home IP every couple weeks, by my latest log check. No need to pay for dynamic dns. Self-hosting is a long journey of solving such trivial problems. But it's pretty rewarding when it all fits together. :) Good luck! I have a setup like the one you desire. Some of my services are port-forwarded to the public internet (i.e. the ones with a login screen) behind a local nginx instance. Others are only available on a "local" network, i.e. at home or via a VPN tunnel advertised at secret-vpn.{}.tld.